This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Building Secondary Languages After Newlib is Installed
- From: Hans-Peter Nilsson <hp at bitrange dot com>
- To: Joel Sherrill <joel dot sherrill at oarcorp dot com>
- Cc: Ralf Corsepius <ralf dot corsepius at rtems dot org>, Andreas Schwab <schwab at redhat dot com>, Ian Lance Taylor <iant at google dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Wed, 9 Feb 2011 01:48:18 -0500 (EST)
- Subject: Re: Building Secondary Languages After Newlib is Installed
- References: <4D41B628.4070009@oarcorp.com> <4D4238D7.1060809@rtems.org> <mcr62t9msji.fsf@google.com> <4D4278D3.8050205@rtems.org> <m362t9xubt.fsf@redhat.com> <4D42A15F.4050304@rtems.org> <4D42D98B.2040203@oarcorp.com>
On Fri, 28 Jan 2011, Joel Sherrill wrote:
> This almost works but libstdc++-v3/configure.ac explicitly
> checks $with_newlib to trip some AC_DEFINE's which have
> to be tripped to build. I have a patch attached that logically
> says if on target X, then you are always using newlib so
> if you have "with_newlib" or "use_newlib", then set the
> AC_DEFINE's. There may be a better way to know if the
> library installed is newlib.
>
> So if --without-newlib is supposed to do the trick, then
> it almost works. I can build Ada, Go, and C++ with
> --without-newlib and this patch or something similar
> but better.
It looks like libstdc++-v3 mistakenly uses with_newlib to mean
that the target uses newlib, not just that newlib is being built
in this tree (which is how toplevel configure uses it).
brgds, H-P