crossdev -t x86_64-pc-linux-gnu ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- * Host Portage ARCH: x86 * Target Portage ARCH: amd64 * Target System: x86_64-pc-linux-gnu * Stage: 3 (C/C++ compiler) * binutils: binutils-[latest] * gcc: gcc-[latest] * headers: linux-headers-[latest] * libc: glibc-[latest] * PORTDIR_OVERLAY: /usr/local/portage * PORT_LOGDIR: /var/log/portage * PKGDIR: /usr/portage/packages/cross/x86_64-pc-linux-gnu * PORTAGE_TMPDIR: /var/tmp/cross/x86_64-pc-linux-gnu _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - * Log: /var/log/portage/cross-x86_64-pc-linux-gnu-binutils.log * Emerging cross-binutils ... [ ok ] * Log: /var/log/portage/cross-x86_64-pc-linux-gnu-gcc-stage1.log * Emerging cross-gcc-stage1 ... [ ok ] * Log: /var/log/portage/cross-x86_64-pc-linux-gnu-linux-headers.log * Emerging cross-linux-headers ... [ ok ] * Log: /var/log/portage/cross-x86_64-pc-linux-gnu-glibc.log * Emerging cross-glibc ... [ ok ] * Log: /var/log/portage/cross-x86_64-pc-linux-gnu-gcc-stage2.log * Emerging cross-gcc-stage2 ... * gcc failed :( * If you file a bug, please attach the following logfiles: * /var/log/portage/cross-x86_64-pc-linux-gnu-info.log * /var/log/portage/cross-x86_64-pc-linux-gnu-gcc-stage2.log Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 62256 [details] cross-x86_64-pc-linux-gnu-gcc-stage2.log
Created attachment 62257 [details] cross-x86_64-pc-linux-gnu-info.log
looks like multilib crap
(In reply to comment #3) > looks like multilib crap Ok, as you suggest to pass with i686 on x86_64, except for cross-compiling?..
I have the same error. Athlon XP -> Athlon 64 My athlon 64 multilib is crapped, and I cannot re-emerge glibc. Trying to build a glibc in my XP to fix the 64 bit machine, to no avail.
Got the same problem. Possible solution (not jet tested) : gcc always configures with --enable-multilib, no matter the USE flag (-multilib) The linker problem definately looks like a multilib problem. glibc is not prepared for multilib, does not support it at all. => remove --enable-multilib from configure options
(In reply to comment #6) > Got the same problem. > > Possible solution (not jet tested) : > gcc always configures with --enable-multilib, no matter the USE flag (-multilib) > The linker problem definately looks like a multilib problem. > glibc is not prepared for multilib, does not support it at all. > > => remove --enable-multilib from configure options Tested it with a manual build, WORKS. Pls fix in the ebuild, or wherever this option comes from.
latest sync should handle multilib properly
