| Summary: | [uclibc/toolchain]broken symlinks | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Krzysztof Sywula <Krzysztof.M.Sywula> |
| Component: | core | Assignee: | Richard Purdie <richard.purdie> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Medium+ | CC: | alexandrux.palalau, jessica.zhang, meta.mr.watcher, meta.watcher, raj.khem, richard.purdie |
| Version: | 1.4.1 | ||
| Target Milestone: | 1.5 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Krzysztof Sywula
2013-08-16 17:25:53 UTC
At a quick glance, it looks like you have the uclibc-dbg package installed and most of the broken include symlinks are in that package. The others are in the bin/sbin directories and are likely caused by the update-alternatives usage. The sbin and bin directories aren't much use in an SDK sysroot and can safely be deleted. The uclibc-dbg package needs more investigation. Are you deliberately installing it? The other broken links are initscript related and again, are not needed in typical SDK/ADT usage. (In reply to comment #1) > At a quick glance, it looks like you have the uclibc-dbg package installed > and most of the broken include symlinks are in that package. The others are > in the bin/sbin directories and are likely caused by the update-alternatives > usage. The sbin and bin directories aren't much use in an SDK sysroot and > can safely be deleted. The uclibc-dbg package needs more investigation. Are > you deliberately installing it? > > The other broken links are initscript related and again, are not needed in > typical SDK/ADT usage. there seems to be an uclibc build behavior that we need to get along. It creates certain symlinks during build under libc/include which essentially are then symlinked again for external APIs but the libc/include symlinks point into specific headers inside libc which are not copied over into -dev package only symlinks are copied over. So the fix would be to not copy symlinks but to copy the sources they point to, I havent had time thus far to deeply look into it. I will have some by end of this week. The uclibc problem is resolved with http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=694f034ec0865a0e9f9d5031ca9b0073ff735713 but the other dangling symlink issues remain. I've confirmed that for meta-toolchain in master we no longer have any dangling symlinks so from that perspective the bug is now resolved. In the output listed below, it looks like an image target where some binaries and init scripts were pulled in. In that case its expected there would be some bad links since the postinstalls were not run. I'm guessing its more like bitbake core-image-minimal -c populate_sdk ? http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=bd3164b9e65a96b2aac1061365597442eac5559c resolves absolute symlinks in the target sysroot. The remaining symlinks in the images are correct. Verified on master branch. Commit ID: faf8f8660fae26a14578738b642fdeb08bcb9d54 |