Summary: | cross-i686-pc-linux-gnu/glibc fails on amd64 system; even with crossdev-20110310 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Joe Breuer <gentoo> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | christian.pontesegger, gentoo.guillaume, matthias.mh.herrmann, pappy_mcfae |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
cross-i686-pc-linux-gnu-info.log
cross-i686-pc-linux-gnu-glibc.log cross-i686-pc-linux-gnu/glibc-2.11.3/work/build-default-i686-pc-linux-gnu-nptl/config.log cross-i686-pc-linux-gnu/glibc-2.11.3/work/build-default-i686-pc-linux-gnu-nptl/config.log without distcc |
Description
Joe Breuer
2011-03-19 14:37:07 UTC
Created attachment 266507 [details]
cross-i686-pc-linux-gnu-info.log
Created attachment 266511 [details]
cross-i686-pc-linux-gnu-glibc.log
Created attachment 266513 [details]
cross-i686-pc-linux-gnu/glibc-2.11.3/work/build-default-i686-pc-linux-gnu-nptl/config.log
BTW, compiling/using a 'stable' crossdev toolchain for i686-pc-linux-gnu on my amd64 system used to work; IIRC I last actively used this in September - November 2010. This happens on two different, but similar, gentoo 10.0 amd64 installs for me. Created attachment 266521 [details]
cross-i686-pc-linux-gnu/glibc-2.11.3/work/build-default-i686-pc-linux-gnu-nptl/config.log without distcc
I've just seen distcc piping up in there; and tried again with 'FEATURES="-distcc"'.
Now distcc no longer shows up in the log, but the problem stays exactly the same.
I've found that modification : http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-libs/glibc/files/eblits/common.eblit?r1=1.16&r2=1.17 workaround : revert the file to the older one already been fixed I can confirm that 'crossdev -S i686-pc-linux-gnu' now works on my amd64 system. I can also report that the work around works. Thanks. *** Bug 360195 has been marked as a duplicate of this bug. *** *** Bug 360195 has been marked as a duplicate of this bug. *** |