It seems upgrading my older ARM installation isn't working as it can't compile glibc... /var/tmp/portage/sys-libs/glibc-2.14.1-r3/work/build-default-armv4l-unknown-linux-gnu-nptl/elf/librtld.os:(.ARM.exidx+0x0): undefined reference to `__aeabi_unwind_cpp_pr0' /var/tmp/portage/sys-libs/glibc-2.14.1-r3/work/build-default-armv4l-unknown-linux-gnu-nptl/elf/librtld.os:(.ARM.exidx+0x18): undefined reference to `__aeabi_unwind_cpp_pr1' collect2: ld returned 1 exit status distcc[31841] ERROR: compile (null) on localhost failed I've read this is because of OABI, rather than EABI. But I've read that Gentoo supports both. Is there anything I can do for OABI support ?
i built glibc-2.14.1-r2 just fine for arm OABI. are you using distcc nodes that have EABI toolchains ? btw, OABI isn't supported with >=glibc-2.16. upstream has removed support for it, and i see no reason to continue supporting it. armv4 (no thumb) should work with EABI, and that's the min CPU we really care about.
No, not using distcc at all.
Maybe OABI isn't supported in 2.14 ?
Also, I thought eabi toolchains had armv4l-unknown-linux-gnueabi- prefix, so the compiler would be called differently anyway. Is there any guide to convert from OABI to EABI, or is a complete re-install ?
(In reply to comment #4) yes, eabi toolchains end in "gnueabi" while oabi end in "gnu". you provided very little information, so i can't say what's going wrong. but we know OABI is EOL in upstream toolchain packages, so it's probably best to migrate rather than debug a package that is no longer latest stable. unfortunately, OABI->EABI is best done as a complete re-install. it (like pretty much everything) could be accomplished in a live migration, but there is no documentation that i know of to assist in that.
