Fix for unexpected failure in ld-cris/warn3

Hans-Peter Nilsson hp@bitrange.com
Tue Mar 1 17:34:00 GMT 2005


Hi Nick

On Tue, 1 Mar 2005, Nick Clifton wrote:
> With a toolchain configured as --target=cris-elf and built
> on an x86_64 host running Linux I saw these messages in the ld.log when
> running the linker tests:
>
>    succeeded with: <>, expected: <warning: isatty is not implemented and
> will always fail$>
>    FAIL: ld-cris/warn3

Thanks.  I have not seen this in autotester runs on
i686-pc-linux-gnu cross to cris-axis-elf.  Maybe it's a
64-bit-host thingy; the test for the warning failing there.
I'll try and get hold of one and test there.

>  From looking at the warn3.d and warn4.d files I had thought that one
> was intended to be run for the cris-elf target and another for the
> cris-aout target.  Obviously I was wrong.

They're indeed meant for a.out and ELF, but as the assembler and
linker support both formats, both tests run on both cris-*-elf
and cris-*-aout.  Maybe a bit confusing if you're not used to
GAS being multiformat. :-)

> Incidentally I do not normally test the cris-aout target but whilst
> investigating this problem I thought that it would be a good idea to
> check.  It seems to generate quite a lot of unexpected failures in the
> linker's ld-cris testsuite, most of which are due to this error message:
>
>    Error: --no-underscore is invalid with a.out format

Thanks.  I do not normally test cris-aout but will do so and fix
stragglers.

brgds, H-P



More information about the Binutils mailing list