This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: possible bug with install-headers make target
On Thu, Jul 9, 2009 at 1:51 PM, Mike Frysinger<vapier@gentoo.org> wrote:
> this is a weak circular argument. ?the C library must cater to building up a
> cross-toolchain and to do that, you have to be able to install just the
> headers. ?you cant build the libraries and thus the headers without first
> installing the headers and building a full gcc C compiler.
The C library definitely does not cater (thought it should) to
building up a cross-toolchain, EGLIBC does, and it has fixes for
installing headers.
>> To claim the install-headers target is broken you would have to claim
>> that it was designed for some purpose.
>
> Ryan's claims seems pretty logical to me, as is the implied install-headers
> purpose (i dont think there is any *documented* purpose)
The project needs an internals manual to clear up issues like this
one. I've added this to my wishlist on the wiki.
>> You could claim that it's only purpose is to install a minimal set of
>> headers for rebuilding gcc, and if it does that correctly, then
>> nothing is wrong (even if features.h is not installed).
>
> it doesnt work correctly. ?look at any package out there that builds cross
> compilers and you'll find plenty of workarounds to make the headers-install
> step work (including, but not limited to, screwing around with the configure
> script).
> -mike
Yes, you're right, I do see that I've got some local hacks for several
headers when using non-EGLIBC sources.
Cheers,
Carlos.