This is the mail archive of the crossgcc@sources.redhat.com 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 Saturday 09 April 2005 09:54 am, Dimitry Andric wrote: > On 2005-04-09 at 02:11:11 Mike Frysinger wrote: > > communicating in the kernel-requires-gcc-but-gcc-requires-kernel thread > > ... > > IIRC, it's even: > > - gcc requires libc headers > - libc requires kernel headers > - kernel headers require gcc > > :) > > So the reason crosstool sets up kernel headers (whether sanitized or > not) is to make the basic glibc header setup (with --hacker-mode, etc) > work, which in turn makes the base gcc build possible, even if the > --without-headers feature is broken. ive personally built base gcc (C-only) w/out libc or kernel headers for: alpha arm / armeb avr hppa / hppa64 i[3456]86 m68k mips / mips64 / mipsel / mips64el powerpc / powerpc64 (the later now possible thanks to Khem Raj) s390 / s390x sh / sheb / sh4 / sh4eb / sh64 sparc / sparc64 the only one i have yet to get to work really is ia64 ... i know headers arent required because i do it all the time now ;) -mike ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |