Re: sys-include/newlib.h

[Jeff Johnston <jjohnstn at redhat dot com>]

I did not know you were specifying --with-newlib, but should have surmised it.

What isn't supported is specifying headers from the newlib source directory (i.e.
unconfigured headers) and expecting to properly compile code.  Is it possible
to point to an empty directory to skirt the inhibit_libc check and use the target/include
headers that you say are on the include path and built as part of configuration?

-- Jeff J.

----- Original Message -----
> Hi Jeff,
> 
> > What you are trying is unsupported.  Newlib configuration needs to run.
> > Have you tried --with-newlib?  You might need to add a
> > configure-target-newlib or all-target-newlib target to your configure call.
> 
> I'm not sure what you mean by newlib configuration needs to run. I thought it
> was, and that's what is generating target/include/newlib.h (which has the
> correct values generate by configure).
> 
> Yes, I'm using --with-newlib. This is with newlib & gcc source trees merged,
> so they configure and build together.
> 
> Do you mean --with-headers is unsupported? If I don't use that, then
> inhibit_libc=true is set in gcc/Makefile, and things like gprof support
> aren't built.
> 
> Here's the code from gcc/configure.ac
> 
> if { { test x$host != x$target && test "x$with_sysroot" = x ; } ||
>        test x$with_newlib = xyes ; } &&
>      { test "x$with_headers" = xno || test ! -f "$target_header_dir/stdio.h";
>      } ; then
>        inhibit_libc=true
> 
> Is that not saying it needs to be set?
> 
> Thanks,
> Jon
>  
> 
>