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 2/19/06, Trevor Harmon <trevor@vocaro.com> wrote: > > On 2/19/06, Trevor Harmon <trevor@vocaro.com> wrote: > >> Crosstool supports "sanitized Linux headers". What exactly is a > >> "sanitized" header? > > > > It's a kernel header cleansed of any details not needed by glibc. > > There have been many such sanitized header packages; the one > > I use is at http://ep09.pld-linux.org/~mmazur/linux-libc-headers/ > > and seems to be popular. > > Okay, so in other words sanitized headers are used only for > bootstrapping glibc? I assume I can delete them once glibc has been > successfully compiled? I think so. Or you could leave them there. I do. Perhaps it'll bite me someday, but it hasn't yet. > >> Also, in crosstool-0.38, many (all?) of the .dat files specify both > >> LINUX_SANITIZED_HEADER_DIR and LINUX_DIR. ... > > But normally one would use identical versions, right? Isn't it > possible that if I specify different numbers, then the LINUX_DIR > tests could fail simply because the version is too old/new? Nope. Being able to cross-compile a kernel doesn't depend on the interface to the kernel on the target system. Cross-compiling a kernel doesn't need the target's libc at all, in fact. (Unless you count klibc!) - Dan -- Wine for Windows ISVs: http://kegel.com/wine/isv ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.org
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |