Re: Armhf dynamic linker path
On 2 May 2012 05:15, Michael Hope wrote: > On 27 April 2012 11:59, Michael Hope wrote: >> On 23 April 2012 14:23, Jon Masters wrote: >>> On 04/22/2012 06:06 PM, Michael Hope wrote: On 21 April 2012 09:10, Jon Masters wrote: > Hey everyone, > > Following up here. Where do we stand? We need to have upstream patches > before we can pull them into the distro - is that piece done? Hi Jon. I've been away, sorry. I've just sent the GCC patch and Carlos is on the hook for the GLIBC side. >>> >>> I saw the email. Could folks do me a favor and let me know the moment >>> this lands in upstream and I'll arrange for us to pull it immediately. >>> >>> (I'm on all the libc lists, but then I'm on almost every list, >>> everywhere, so it takes a bit of time to get to it) >> >> Hi Jon. There's a fault with the GCC patch so it's still in progress. >> Carlos sent the GLIBC patch out for review today. > > Hi Jon. The GCC patch is now upstream as r186859 and r187012. I noticed that it now sets the dynamic loader to /lib/ld-linux-armhf.so.3 even when configured for soft-float ABI and linking against a soft-float rootfs. The resulting binaries then fail to run. Passing -mfloat-abi=softfp to the link command fixes it. Is this change in behaviour intentional? -- Mans Rullgard / mru ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Armhf dynamic linker path
On 02/05/12 13:25, Mans Rullgard wrote: > On 2 May 2012 05:15, Michael Hope wrote: >> On 27 April 2012 11:59, Michael Hope wrote: >>> On 23 April 2012 14:23, Jon Masters wrote: On 04/22/2012 06:06 PM, Michael Hope wrote: > On 21 April 2012 09:10, Jon Masters wrote: >> Hey everyone, >> >> Following up here. Where do we stand? We need to have upstream patches >> before we can pull them into the distro - is that piece done? > > Hi Jon. I've been away, sorry. I've just sent the GCC patch and > Carlos is on the hook for the GLIBC side. I saw the email. Could folks do me a favor and let me know the moment this lands in upstream and I'll arrange for us to pull it immediately. (I'm on all the libc lists, but then I'm on almost every list, everywhere, so it takes a bit of time to get to it) >>> >>> Hi Jon. There's a fault with the GCC patch so it's still in progress. >>> Carlos sent the GLIBC patch out for review today. >> >> Hi Jon. The GCC patch is now upstream as r186859 and r187012. > > I noticed that it now sets the dynamic loader to /lib/ld-linux-armhf.so.3 > even when configured for soft-float ABI and linking against a soft-float > rootfs. The resulting binaries then fail to run. Passing -mfloat-abi=softfp > to the link command fixes it. Is this change in behaviour intentional? > Eh? Exactly what command line did you invoke the compiler with, and what was the configuration? Are you sure you don't have a compiler configured to hard-float by default? R. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Armhf dynamic linker path
On 2 May 2012 13:42, Richard Earnshaw wrote: > On 02/05/12 13:25, Mans Rullgard wrote: >> On 2 May 2012 05:15, Michael Hope wrote: >>> On 27 April 2012 11:59, Michael Hope wrote: On 23 April 2012 14:23, Jon Masters wrote: > On 04/22/2012 06:06 PM, Michael Hope wrote: >> On 21 April 2012 09:10, Jon Masters wrote: >>> Hey everyone, >>> >>> Following up here. Where do we stand? We need to have upstream patches >>> before we can pull them into the distro - is that piece done? >> >> Hi Jon. I've been away, sorry. I've just sent the GCC patch and >> Carlos is on the hook for the GLIBC side. > > I saw the email. Could folks do me a favor and let me know the moment > this lands in upstream and I'll arrange for us to pull it immediately. > > (I'm on all the libc lists, but then I'm on almost every list, > everywhere, so it takes a bit of time to get to it) Hi Jon. There's a fault with the GCC patch so it's still in progress. Carlos sent the GLIBC patch out for review today. >>> >>> Hi Jon. The GCC patch is now upstream as r186859 and r187012. >> >> I noticed that it now sets the dynamic loader to /lib/ld-linux-armhf.so.3 >> even when configured for soft-float ABI and linking against a soft-float >> rootfs. The resulting binaries then fail to run. Passing -mfloat-abi=softfp >> to the link command fixes it. Is this change in behaviour intentional? > > Eh? Exactly what command line did you invoke the compiler with, and > what was the configuration? Are you sure you don't have a compiler > configured to hard-float by default? It happens even with the simplest possible "arm-linux-gnueabi-gcc foo.c" command. The compiler is definitely using the soft-float ABI. Output of -v: Using built-in specs. COLLECT_GCC=arm-unknown-linux-gnueabi-gcc-4.8.0 COLLECT_LTO_WRAPPER=/usr/libexec/gcc/arm-unknown-linux-gnueabi/4.8.0/lto-wrapper Target: arm-unknown-linux-gnueabi Configured with: /tmp/portage/cross-arm-unknown-linux-gnueabi/gcc-4.8.0_alpha20120429/work/gcc-4.8-20120429/configure --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/arm-unknown-linux-gnueabi/gcc-bin/4.8.0 --includedir=/usr/lib/gcc/arm-unknown-linux-gnueabi/4.8.0/include --datadir=/usr/share/gcc-data/arm-unknown-linux-gnueabi/4.8.0 --mandir=/usr/share/gcc-data/arm-unknown-linux-gnueabi/4.8.0/man --infodir=/usr/share/gcc-data/arm-unknown-linux-gnueabi/4.8.0/info --with-gxx-include-dir=/usr/lib/gcc/arm-unknown-linux-gnueabi/4.8.0/include/g++-v4 --host=x86_64-pc-linux-gnu --target=arm-unknown-linux-gnueabi --build=x86_64-pc-linux-gnu --disable-altivec --disable-fixed-point --without-ppl --without-cloog --enable-lto --disable-nls --with-system-zlib --disable-werror --enable-secureplt --enable-multilib --disable-libmudflap --disable-libssp --disable-libgomp --with-python-dir=/share/gcc-data/arm-unknown-linux-gnueabi/4.8.0/python --enable-checking=release --disable-libgcj --disable-libquadmath --enable-languages=c,c++ --with-sysroot=/usr/arm-unknown-linux-gnueabi --disable-bootstrap --enable-__cxa_atexit --enable-clocale=gnu --with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.8.0_alpha20120429' Thread model: posix gcc version 4.8.0 20120429 (experimental) (Gentoo 4.8.0_alpha20120429) -- Mans Rullgard / mru ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Armhf dynamic linker path
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 02 May 2012 00:39:37 -0400 Jon Masters wrote: > On 05/02/2012 12:15 AM, Michael Hope wrote: > > On 27 April 2012 11:59, Michael Hope > > wrote: > >> On 23 April 2012 14:23, Jon Masters wrote: > >>> On 04/22/2012 06:06 PM, Michael Hope wrote: > On 21 April 2012 09:10, Jon Masters wrote: > > Hey everyone, > > > > Following up here. Where do we stand? We need to have upstream > > patches before we can pull them into the distro - is that piece > > done? > > Hi Jon. I've been away, sorry. I've just sent the GCC patch and > Carlos is on the hook for the GLIBC side. > >>> > >>> I saw the email. Could folks do me a favor and let me know the > >>> moment this lands in upstream and I'll arrange for us to pull it > >>> immediately. > >>> > >>> (I'm on all the libc lists, but then I'm on almost every list, > >>> everywhere, so it takes a bit of time to get to it) > >> > >> Hi Jon. There's a fault with the GCC patch so it's still in > >> progress. Carlos sent the GLIBC patch out for review today. > > > > Hi Jon. The GCC patch is now upstream as r186859 and r187012. > > Yup. I think Dennis has pinged Jakub about it. Dennis, do we need to > do anything else on our end? I think we've got the symlink handled, > etc.? > > Jon. Jakub will pull tha patches in when glibc is also fixed. Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAk+hcSYACgkQkSxm47BaWffD/wCdEz7teWUXTmvPa8Z8gAVLC74Y cgoAoJz5OV/8VTu5agXMR8oUxIgDRkfa =oKEH -END PGP SIGNATURE- ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Armhf dynamic linker path
On 05/02/2012 01:38 PM, Dennis Gilmore wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Wed, 02 May 2012 00:39:37 -0400 > Jon Masters wrote: > >> On 05/02/2012 12:15 AM, Michael Hope wrote: >>> On 27 April 2012 11:59, Michael Hope >>> wrote: On 23 April 2012 14:23, Jon Masters wrote: > On 04/22/2012 06:06 PM, Michael Hope wrote: >> On 21 April 2012 09:10, Jon Masters wrote: >>> Hey everyone, >>> >>> Following up here. Where do we stand? We need to have upstream >>> patches before we can pull them into the distro - is that piece >>> done? >> >> Hi Jon. I've been away, sorry. I've just sent the GCC patch and >> Carlos is on the hook for the GLIBC side. > > I saw the email. Could folks do me a favor and let me know the > moment this lands in upstream and I'll arrange for us to pull it > immediately. > > (I'm on all the libc lists, but then I'm on almost every list, > everywhere, so it takes a bit of time to get to it) Hi Jon. There's a fault with the GCC patch so it's still in progress. Carlos sent the GLIBC patch out for review today. >>> >>> Hi Jon. The GCC patch is now upstream as r186859 and r187012. >> >> Yup. I think Dennis has pinged Jakub about it. Dennis, do we need to >> do anything else on our end? I think we've got the symlink handled, >> etc.? >> >> Jon. > > Jakub will pull tha patches in when glibc is also fixed. Right. So then, the question is where we stand with GLIBC, Carlos? Jon. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Armhf dynamic linker path
On Wed, May 2, 2012 at 5:34 PM, Jon Masters wrote: > Right. So then, the question is where we stand with GLIBC, Carlos? It's going through Mentor's build/test cycle right now with the new gcc patch and a revised glibc patch. Cheers, Carlos. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Armhf dynamic linker path
On 05/02/2012 09:24 PM, Carlos O'Donell wrote: > On Wed, May 2, 2012 at 5:34 PM, Jon Masters wrote: >> Right. So then, the question is where we stand with GLIBC, Carlos? > > It's going through Mentor's build/test cycle right now with the new > gcc patch and a revised glibc patch. Did I mention you rock? In case I neglected it. You rock. And so does Michael, and Steve, and Dennis, and in fact everyone rocks. Beer next time I see any of you (and more coffee for me!) Jon. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
