It seems to build glibc without errors and then at the end: make[1]: Leaving directory `/var/tmp/cross/i686-unknown-linux-gnu/portage/glibc-2.3.6-r2/work/glibc-2.3.6' prepallstrip: strip: i686-unknown-linux-gnu-strip --strip-unneeded /usr/i686-unknown-linux-gnu/lib/libanl-2.3.6.so /usr/i686-unknown-linux-gnu/lib/libBrokenLocale-2.3.6.so /usr/i686-unknown-linux-gnu/lib/libpcprofile.so /usr/i686-unknown-linux-gnu/lib/libnss_hesiod-2.3.6.so /usr/i686-unknown-linux-gnu/lib/libSegFault.so /usr/i686-unknown-linux-gnu/lib/libcidn-2.3.6.so /usr/i686-unknown-linux-gnu/lib/libnsl-2.3.6.so /usr/i686-unknown-linux-gnu/lib/libdl-2.3.6.so /usr/i686-unknown-linux-gnu/lib/libnss_compat-2.3.6.so /usr/i686-unknown-linux-gnu/lib/libcrypt-2.3.6.so /usr/i686-unknown-linux-gnu/lib/libnss_files-2.3.6.so /usr/i686-unknown-linux-gnu/lib/libc-2.3.6.so /usr/i686-unknown-linux-gnu/lib/libpthread-2.3.6.so /usr/i686-unknown-linux-gnu/lib/libnss_nisplus-2.3.6.so /usr/i686-unknown-linux-gnu/lib/libm-2.3.6.so /usr/i686-unknown-linux-gnu/lib/ld-2.3.6.so /usr/i686-unknown-linux-gnu/lib/libmemusage.so /usr/i686-unknown-linux-gnu/lib/libnss_dns-2.3.6.so /usr/i686-unknown-linux-gnu/lib/libresolv-2.3.6.so /usr/i686-unknown-linux-gnu/lib/libnss_nis-2.3.6.so /usr/i686-unknown-linux-gnu/lib/libutil-2.3.6.so /usr/i686-unknown-linux-gnu/lib/libthread_db-1.0.so /usr/i686-unknown-linux-gnu/lib/librt-2.3.6.so cp: cannot stat `/var/tmp/cross/i686-unknown-linux-gnu/portage/glibc-2.3.6-r2/temp/strip-backup/*': No such file or directory I tried i386-unknown-linux-gnu and i686-unknown-linux-gnu with glibc-2.3.6-r2 and glibc-2.3.5-r3 with the same results.
Created attachment 77510 [details] glibc log
Created attachment 77511 [details] info log
*** This bug has been marked as a duplicate of 89279 ***
I don't see the relationship between this bug and 89279. Anyway I tried to emerge libunwind (even if no error mentions missing libunwind) but it didn't solve the problem. If this is really a duplicate of 89279, which I doubt, can you please explain me what is needed to fix it?
your typo threw me off i thought it was 'ia64' at any rate, your bug was fixed in cvs already, do you have an old checkout ?
no, but I can wait for it to be released. The ix86 was meant to indicate i386, i686 etc... sorry if it was misleading and thanks for the support
then sync up and it'll start working magically