[haiku-development] Re: Include path for glibc-specific stuff?

On 2009-06-30 at 10:44:45 [+0200], Oliver Tappe <zooey@xxxxxxxxxxxxxxx> wrote:
> Hi there,
> 
> as I'm still working on the compilers, here's another question:
> 
> I'd like to introduce the glibc-specific 'printf.h' header, since our libroot
> contains the respective functions and we pretend to support those, too, by
> declaring _G_HAVE_PRINTF_FP in _G_config.h.

Having looked a bit more at printf_size and friends, and having learnt that it 
really is implemented by glibc only, I am going to try and find a way around 
it during the native build of haiku's libstdc++. If I manage to do that, I'm 
going to remove the respective functions from libroot.
If I can't figure that out, I'd like to follow Ingo's suggestion in a 
corresponding ticket and just leave it alone and copy libstdc++.r4.so from the 
cross build - *if* gcc4 has no such dependency (and I doubt it has).

> But I suppose both headers (printf.h and _G_config.h) should live in a
> special folder, as they are not POSIX. Judging by BEINCLUDES, we could revive
> 'headers/gnu' or shall we go for 'headers/glibc' instead?
> 
> Do you know of any other, existing headers that should be moved there?

Those questions are still valid, though.

cheers,
        Oliver

Other related posts: