| Summary: | Cross-compilation issue with libexec when building for 32 bit host on arch 64. | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Other YP Layers | Reporter: | Laszlo Papp <lpapp> | ||||||||
| Component: | layers | Assignee: | Christopher Larson <kergoth> | ||||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||||
| Severity: | normal | ||||||||||
| Priority: | Medium | CC: | kergoth, meta.mr.watcher, meta.watcher, poky.bs.watcher, poky.watcher, ross.burton, sgw | ||||||||
| Version: | unspecified | ||||||||||
| Target Milestone: | 1.5 | ||||||||||
| Hardware: | x86 | ||||||||||
| OS: | Multiple | ||||||||||
| Whiteboard: | |||||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||||||
| Attachments: |
|
||||||||||
|
Description
Laszlo Papp
2013-07-26 07:57:11 UTC
Created attachment 1369 [details]
bblayers.conf
Created attachment 1370 [details]
installed-packages
The main problem seems to be the fact that the libexec folder desired contains only an empty folder. Unfortunately when we use git for having a back up for our toolchain, empty folders get lost, of course. Question is, why would meta-sourcery like to introspect an empty folder and demand it? Can this check be removed, please? It copies paths it knows exists in the release. It's not empty in most versions of the toolchain, and the path does exist in the release toolchain you're using, so it's completely reasonable to copy a path we know exists. I'll add a check to work around libexec not existing for your case. For the love of God, please do not copy empty folders. They do not make any sense. If you do, do not release a toolchain with empty folders pretty please. Git and several other storages will drop the content of empty directories altogether. By the way, the oe-core sourcery support works just fine with denzil, so this libexec enforcement seems to have happened after that. I believe it should work, at least for empty folders, like oe-core sourcery support. That would probably unblock me. I cannot do much about git not tracking files, but content. This should now be resolved, please confirm, thanks. OK, thanks. Hopefully, I can do that on Monday. typically the assignee changes the status of the bugs, not the reporter. Sure, but I think Chris forgot to change, so in this special case, he just got some help. I think this kind of help is to be appreciated rather than discouraged. Laszlo, ping on Chris's request to verify the fix. To be honest, I do not have time in the foreseeable future to verify this, but if I recall correctly, I checked this back then. I think it is ok to close this, and I will try to reopen if the issue is still hit. |