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: > Lennert Buytenhek said the following on 12/5/2006 7:10 PM: > > The kernel itself needs to be EABI to be able to run EABI userland > > binaries. > > > I dont think so. You can have kernel compiled with Old ABI compiler and it > still will run EABI binaries with right config options. No. > it might needs some wrappers in glibc though. This is (was) a hack. And with those glibc wrappers an EABI binary just pretended to be old ABI and was seen as old ABI by the kernel. > How would you generate a EABI binary with a non EABI toolchain then. (after > all kernel is also a binary) There is the "toolchain", ant there is the "compiler". The kernel only needs a "compiler" (well and a linker of course). You don't need glibc to compile a kernel. The compiler can select between both ABIs at runtime. At least enough of the ABI differences the kernel cares about can be selected at runtime. So any gcc with EABI support can do regardless of how it was configured. 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] |