Re: Building Secondary Languages After Newlib is Installed

[Joel Sherrill <joel dot sherrill at oarcorp dot com>]

On 01/28/2011 04:58 AM, Ralf Corsepius wrote:
> On 01/28/2011 10:15 AM, Andreas Schwab wrote:
> > Ralf Corsepius<ralf.corsepius@rtems.org>   writes:
> >
> > > - Remove newlib from the source tree
> > --without-newlib should probably be enough.
> Good point, agreed.
>
> In case of Joel and rtems the situation probably can be furtherly
> simplified:
>
> RTEMS has gcc-4.5.5-compiled newlib-rpms - Provided the set of multilibs
> hasn't changed (and gcc hasn't changed too much), it probably will
> suffice to install these newlib rpms and use them to build gcc against them.
That's true but I want to ensure that the GCC head does indeed
compile newlib and RTEMS with the GCC head.

> On 01/28/2011 03:15 AM, Andreas Schwab wrote:
> > --without-newlib should probably be enough.
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.

> Ralf


--
Joel Sherrill, Ph.D.             Director of Research&  Development
joel.sherrill@OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985

Attachment: libstc++.diff
Description: Text document