Re: arrgh. can't install headers in glibc-2.3.2.

[Peter Barada <peter at baradas dot org>]

>>>The problem is that I tried to fool glibc-2.3.2 into installing its headers
>>>with a native compiler instead of a cross compiler, but it looks like
>>>that fails in this one spot.
>>>
>>>Arrgh.  I'm starting to wonder if it's at all possible to build
>>>a cross compiler with glibc-2.3.2.
>> 
>> Suppose we suppress building libgcc ...
>
>The problem happens before that, it's when glibc is trying to generate some
>headers using the compiler as a way to extract info from the source.
>I got around the previous problem by disabling linuxthreads and sanity checks
>when configuring glibc the first time (the bootstrap compiler doesn't need
>threads, does it?), but ran into another problem.

If I understand this correctly we need glibc headers to build a 
bootstrap compiler since the headers are required for libgcc1/2, exception
handling(stack unwind, etc), but those libraries are *not* necessary to build
glibc (or at least glibc-2.2.5).

Suppose we hack gcc to suppress the construction of ligbcc, etc if its
configured to build a bootstrap (or we make a different Makefile
target, or we hack the Makefile directly).

Then we could build a bare-bones bootstrap that *should* be able to
build glibc, and then go back and build up a full compiler.

If I comment out the two sets of lines in the generated gcc/Makefile
that define LIBGCC and INSTALL_LIBGCC (arond lines 383 and 688) then
libgcc is *not* build and the bootstrap installs correctly...

Do you think this approach might work?

-- 
Peter Barada
peter@baradas.org

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com