On 01/27/2011 07:15 PM, Joel Sherrill wrote:
Hi,
There are now 14 RTEMS targets which I try to
test regularly on the head. Where possible,
I try to test C, C++, Ada, and Go. The procedure
is roughly
+ build and install C, C++ with newlib multilibed
+ build and install RTEMS
+ build and install C, Adawith newlib multilibed
+ build and install C, Gowith newlib multilibed
This works well but there is no reason to spend
time building newlib over and over. On targets
with lots of multilibs, this takes a long time.
To speed up the Ada and Go builds, I want to use
the newlib installed in the first step and not
build it again. But obviously the configure
scripts have to pick up things correctly.
libstdc++-v3/configure.ac tests $with_newlib to
set a number of flags.
What is the preferred combination of
--enable-newlib and --with-newlib settings
to build with newlib in the gcc source tree
but not build it and use the installed copy
for the Ada and Go builds?
Theoretically, none at all, because building against an installed newlib
should be equivalent to "standard cross-building".
Ralf
