Trying to generate the toolchain to develop applications for an ARM aquitectured platform with Linux, on a x86 host (PC), I run into an error, and the tools are not generated. The crossdev version is 0.9.18-r7. max joseba # crossdev --target arm-linux-gnu -------------------------------------------------------------------------------- * Host Portage ARCH: x86 * Target Portage ARCH: arm * Target System: arm-linux-gnu * Stage: 4 (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/arm-linux-gnu * PORTAGE_TMPDIR: /var/tmp/cross/arm-linux-gnu _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - * Forcing the latest versions of {binutils,gcc}-config/gnuconfig ... [ ok ] * Log: /var/log/portage/cross-arm-linux-gnu-binutils.log * Emerging cross-binutils ... [ ok ] * Log: /var/log/portage/cross-arm-linux-gnu-gcc-stage1.log * Emerging cross-gcc-stage1 ... [ ok ] * Log: /var/log/portage/cross-arm-linux-gnu-linux-headers.log * Emerging cross-linux-headers ... [ ok ] * Log: /var/log/portage/cross-arm-linux-gnu-glibc.log * Emerging cross-glibc ... [ ok ] * Log: /var/log/portage/cross-arm-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-arm-linux-gnu-info.log * /var/log/portage/cross-arm-linux-gnu-gcc-stage2.log
Created attachment 146494 [details] cross-arm-linux-gnu-info.log
Created attachment 146495 [details] cross-arm-linux-gnu-gcc-stage2.log
>>> Original instance of package unmerged safely. /usr/bin/python: error while loading shared libraries: /usr/lib/gcc/arm-linux-gnu/4.2.3/libgcc_s.so.1: ELF file OS ABI invalid * * ERROR: cross-arm-linux-gnu/gcc-4.2.3 failed.
post your /etc/env.d/05gcc and /etc/ld.so.conf files as attachments
Created attachment 147337 [details] ld.so.conf
Created attachment 147338 [details] 05gcc-arm-linux-gnu
(In reply to comment #4) > post your /etc/env.d/05gcc and /etc/ld.so.conf files as attachments > I have posted the files, as you required.
well that doesnt make much sense as the ldconfig files dont include any paths to the arm toolchain post your /etc/profile.env file as an attachment as well as `emerge --verbose --info`
Created attachment 148964 [details] /etc/profile.env
Created attachment 148966 [details] Result for 'emerge --verbose --info'
(In reply to comment #8) > well that doesnt make much sense as the ldconfig files dont include any paths > to the arm toolchain > > post your /etc/profile.env file as an attachment as well as `emerge --verbose > --info` > There you have.
hrm, looks like this dates back to some crap eradicator merged in and i didnt notice: http://sources.gentoo.org/eclass/toolchain.eclass?r1=1.71&r2=1.72 gcc-compiler_pkg_postinst() { export LD_LIBRARY_PATH=${LIBPATH}:${LD_LIBRARY_PATH} that's clearly wrong
dropped the relevant line in cvs http://sources.gentoo.org/eclass/toolchain.eclass?r1=1.350&r2=1.351