| Summary: | sys-libs/uclibc ebuild should create a link to /lib/ld-linux.so but doesn't | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Wolfgang Draxinger <wdraxinger> |
| Component: | New packages | Assignee: | Embedded Gentoo Team <embedded> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
any gcc that sets the ld-linker to /lib/ld-linux.so is not a uClibc targeted gcc and is not supported build a proper toolchain (In reply to comment #1) > any gcc that sets the ld-linker to /lib/ld-linux.so is not a uClibc targeted > gcc and is not supported > > build a proper toolchain Tell that the gcc build system, that fails, if that link isn't present. It seems like some build related programs have the reference to ld-linux.so hardcoded. Having that link will make the gcc build complete. If it's not the uclibc install ebuild, then something in the uclibc patches for gcc is missing. maybe you should actually describe your system and your problem instead of saying "it fails" and citing some non-descriptive symptoms my uclibc targetted toolchains have no problem invoking the proper ldso (In reply to comment #3) > maybe you should actually describe your system and your problem instead of > saying "it fails" and citing some non-descriptive symptoms > > my uclibc targetted toolchains have no problem invoking the proper ldso Ok, here are the steps, that cause problems on my system (very reproducible indeed). Download any uclibc stage (so it for stage 3). Unpack the stage to $root_fs. mount --bind proc, dev, sys and the portage tree to $root_fs chroot $root_fs, env-update, source /etc/profile emerge -uD system emerge gcc watch the gcc build process fail (the log will show, that a program which name starts with "gen...", e.g. "genmodes" failes with a file not found error. That file not found is ld-linux.so) How am I supposed to use a propper toolchain, if I even can't build it? better, but not quite there what version of gcc ? what architecture ? `emerge --info` ? what stage ? what did the system -uD upgrade ? |
Some programs have certain library paths hardcoded. For example when building gcc a few helper programs a created that have a hardcoded reference to /lib/ld-linux.so(.*) So the uclibc ebuild should create a link(s) from ld-uClibc-*.so to ld-linux.so(.2) That solves many problems Reproducible: Always Steps to Reproduce: 1. download any uclibc stage 2. update uclibc 3. try to build gcc Actual Results: gcc build will fails due to nonexecutability of a intermediate helper program (at me it was ${builddir}/gcc/build/genmodes) Expected Results: gcc should build fine after adding that link manually gcc builds fine