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] |
On Tue, 5 Dec 2006, Khem Raj wrote: > I guess there are two things here. > > 1. The kernel is capable of running EABI binaries. > > For this case you do not require a EABI toolchain so configuring gcc with > arm*-*-linux-gnu would do. Exact. > 2. Kernel itself it compiled as EABI binary. > > This would need a complete EABI toolchain. (configure with > arm*-*-linux-gnueabi ) Untrue. First, for the kernel to be able to execute EABI binaries, it must itself be an EABI binary. So (1) implies(2). But because the kernel is self contained, i.e. it doesn't need any external libraries besides those provided a part of the kernel source itself (not even libgcc.a), you actually don't need a gcc that is fully configured for EABI. The kernel compilation always provides gcc with the explicit ABI flag and therefore resulting binary will have the needed ABI characteristics. Nicolas -- 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] |