[PATCH] PR other/32154

[Richard Sandiford]

Rask Ingemann Lambertsen <rask@sygehus.dk> writes:
> 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.
>
>    For mipsisa64-elf, the linker only warns that _start wasn't found and
> exits 0, so configure seems to work. That could be a bug or pure fluke; I
> don't know. I would not have been surpriced had the linker errored out
> because e.g. _exit wasn't found.

OK, I clearly didn't know what I was talking about.  Sorry for the noise.

Richard