| Summary: | sys-apps/coreutils build failure on Fedora release 16 (Verne) | ||
|---|---|---|---|
| Product: | Gentoo/Alt | Reporter: | Richard Yao (RETIRED) <ryao> |
| Component: | Prefix Support | Assignee: | Gentoo Prefix <prefix> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | Keywords: | REGRESSION |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | sys-apps/coreutils-8.17 build failure | ||
For some reason, I was under the impression that /usr/lib64/libcrypt.so was a linker script on Gentoo, but it also appears to be a symlink. That rules that out as a possible cause. I need the gcc invocation to see what exactly gets passed onto the linker |
Created attachment 327562 [details] sys-apps/coreutils-8.17 build failure I have a Gentoo Prefix installation on gcc110.fsffrance.org that used to work well. After some system updates were done, various packages started to fail to build. I did a quick test involving the following file: #include <crypt.h> int main(){ crypt("test","test"); return 0; } `gcc crypt.c -lcrypt` fails with our GCC while it succeeds with the system GCC. The system GCC is "gcc version 4.6.3 20120306 (Red Hat 4.6.3-2) (GCC)" while ours is "gcc version 4.6.3 (Gentoo 4.6.3 p1.7, pie-0.5.2)". The system ld is "GNU ld version 2.21.53.0.1-6.fc16 20110716" while ours is "GNU ld (GNU Binutils) 2.23". /usr/lib64/libcrypt.so is a symlink to ../../lib64/libcrypt.so.1, which could be what is upsetting the linker. I lack root privileges, so I have no way to verify that removing that symlink makes our linker happy.