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] |
hi -- cross-gcc newbie here. i've been lucky enough that someone else has always prepared the toolchain for me. i guess all good things must come to an end. :-) i'm confused about header versions in a cross-gcc environment, and am hoping for some guidance. crosstool provides a bunch of .dat files which represent triplets, if you will, of compiler version, glibc version, and linux header version. so, for instance, if i build gcc 3.4.5 and glibc 2.3.6, crosstool will choose the 2.6.12 linux headers. but if the platform i'm going to be building for is running a 2.4.24 kernel, i may need things that have been sanitized out of those 2.6.12 headers. in that case, i'm tempted to modify the .dat file to reference a 2.4 set of headers. is this the right thing to do? i'm nervous about this because i see that none of the gcc 3.4.x .dat files reference 2.4 headers -- is this by design? as tempting as it is, i'm assuming i shouldn't just build with the "stock" gcc-3.4.5-glibc-2.3.6.dat and replace some or all of the sys-include directory with 2.4 headers, correct? of course, i'd rather my toolchain could be used for either 2.4-based or 2.6-based development, but i'm unsure how to go about this safely. any pointers welcomed -- thanks... paul =--------------------- paul fox, pgf@foxharp.boston.ma.us (arlington, ma, where it's 22.8 degrees) -- 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] |