This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: [PATCH] PR other/32154
On Mon, Jun 25, 2007 at 11:56:39AM -0400, Daniel Jacobowitz wrote:
> On Sat, Jun 23, 2007 at 12:09:30PM +0200, Rask Ingemann Lambertsen wrote:
> > On Sat, Jun 23, 2007 at 09:18:12AM +0100, Richard Sandiford wrote:
> >
> > > Right. The model used in libstdc++ is that this sort of link test
> > > does not need to work for newlib targets; if we can't link a trivial
> > > program, --with-newlib causes tests for C library functons to fall
> > > back to known-good values.
> >
> > It doesn't work that way (any more). If your linker exits with a non-zero
> > exit code linking a trivial program, then libstdc++ fails to configure. It
> > was like this four years ago also, see bug 12019.
>
> No, Richard is mostly right. --with-newlib avoids link tests.
$ mkdir ~/testbuild
$ cd ~/testbuild
$ /n/12/rask/src/all/configure --target=m32r-unknown-elf --with-newlib --enable-languages=c,c++ --disable-{nls,gdb}
$ make
...
checking whether -lc should be explicitly linked in... yes
checking dynamic linker characteristics... no
checking how to hardcode library paths into programs... immediate
checking for shl_load... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
make[1]: *** [configure-target-libstdc++-v3] Error 1
make[1]: Leaving directory `/home/rask/testbuild'
make: *** [all] Error 2
> So do various target triplets.
Examples?
--
Rask Ingemann Lambertsen