This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Valentin Longchamp wrote: > > I'm confused, because I can read that EABI is only after: > >> binutils - from 2.16.92 - already in Debian >> gcc - gcc 4.1.0 (Thumb interworking on armv4t needs 4.1.1) >> glibc - fully upstream in 2.4. Will also be in 2.3.7 >> Earlier glibcs (2.3.6?) support EABI userspace but had > old-style syscalls to work with older kernels (2.6.8-2.6.13ish). >> kernel - eabi support merged after 2.6.15, present in 2.6.16. > > However, with my gcc-3.4.2 glibc-2.3.3 is GNU EABI according > to readelf, > the pre-built on-board system is glibc-2.3.3 too and EABI too (though > unrecognized). So I'm confused. Does crosstool apply backported EABI > patches ? > Correct, ARM EABI support has only gone into the 'official' branches of gcc/binutils/glibc very recently. If you check the archives for this list over the past couple of months, you'll find several crosstool patches to get it working with pre-release binutils, etc. CodeSourcery, OTOH, produced toolchains with EABI support prior to getting it merged into the 'official' branches. http://www.codesourcery.com/gnu_toolchains/arm/ If you can find their previous releases somewhere, and look for one that matches your glibc, you can give that a try. Hope this helps -- Matthew L. Creech -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |