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]

RE: is that "install glibc headers" step in crosstool necessary?


Robert P. J. Day wrote:
> On Wed, 2 Nov 2005, Bill Gatliff wrote:
> 
>> The fact that it doesn't seem necessary anymore suggests that we
>> should at least provide a developer-level option to skip it.  The
>> easier we can provide evidence to the gcc guys that their release
>> are/aren't bootstrap-able, the more likely they'll stay
>> bootstrap-able.
> 
> this is almost certainly a dumb question but, to be able to skip the
> "install glibc headers" step, this suggests that the bootstrap gcc
> should be able to be created using solely the installed kernel
> headers, is that correct?


  Yes, building the bootstrap compiler needs nothing but the headers (and of
course libraries too) for the *host* system that it will run on.

  Whether those are "installed kernel" headers, because you're cross-compiling
from a linux box, or win32 headers when you're building your cross-compiler on
a win32 box, makes no odds; the point is, it's the local system's headers that
are needed, and nothing for/from the *target* is required at all.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


------
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]