[uClibc] Re: frv-uclibc port updates

[Peter S. Mazinger]

On 15 Nov 2004, Alexandre Oliva wrote:

> On Nov  4, 2004, "Peter S. Mazinger" <ps.m at gmx.net> wrote:
> 
> > On 4 Nov 2004, Alexandre Oliva wrote:
> >> On Nov  4, 2004, "Peter S. Mazinger" <ps.m at gmx.net> wrote:
> >> 
> >> > Removing -nostdinc is incorrect, if we do that, we will end up using 
> >> > installed system headers instead of the ones provided by uClibc sources.
> >> 
> >> But if I don't do that, I can't find stddef.h, which is only provided
> >> by the compiler.
> 
> > But if you do that, you'll build against /usr/include/ instead of 
> > uClibc/include.
> 
> You have to -I or -isystem uClibc's header dir, to get it searched
> before the default search dirs.  But simply removing the dir that
> contains GCC-implementation header files such as stddef.h, stdarg.h,
> etc, will just get you a broken build.  Sure enough, if you have
> headers from a different lib in the same dir, and you include them
> without realizing they're not provided by uClibc itself, you lose, but
> the only way around it would be to copy select files from the GCC
> include dir (which may vary from port to port).  I don't think it's
> worth the effort.

I don't think -nostdinc will be removed, because IMHO it is correct.

You should probably compare the frv port w/ some other arch, because mips 
and x86 (these I know for sure) work. Maybe the links are done incorrectly 
for frv (look for headers: in the diff. Makefiles)
 
Peter