I'm using my various autotester setups to check dejagnu HEAD for
the upcoming (wishfully anyway) 1.5.
I'm not used to git, but "git show" says the latest update is
commit 94dbf2fc904ce3446aa513e41edac6a3edaf316d
Author: Ben Elliston <[EMAIL PROTECTED]>
Date: Mon Feb 11 21:48:59 2008 +1100
With that installed, and binutils as of today (exact revision
unlikely critical), cris-elf gets an extra FAIL compared to
dejagnu-1.4.4-11.fc8 (the Fedora 8 package):
Running /tmp/hpautotest-binutils/bsrc/src/ld/testsuite/ld-cris/cris.exp ...
FAIL: ld-cris/warn3
with ld.log containing:
Executing on host: sh -c {./ld-new
-L/tmp/hpautotest-binutils/bsrc/src/ld/testsuite/ld-cris -mcrisaout -o
tmpdir/dump tmpdir/dump0.o tmpdir/dump1.o tmpdir/dump2.o 2>&1} /dev/null
ld.tmp (timeout = 300)
tmpdir/dump1.o:tmpdir/dump1.o:(.text+0x0): warning: isatty is not implemented
and will always fail
succeeded with: <>, expected: <warning: isatty is not implemented and will
always fail$>
succeeded with: <>, expected: <warning: isatty is not implemented and will
always fail$>
FAIL: ld-cris/warn3
At a glance, it seems prune_warnings has become better at
pruning...
The bottom line is, the fix should probably be local to the ld
testsuite, in ld-lib.exp:run_dump_test; either to tweak the
test-case so it doesn't match the libgloss warning from which it
was derived and which prune_warnings now prunes, or not to apply
prune_warnings when a warning or error is expected(!).
So, I guess this is just a heads-up for the dejagnu project,
with an intent of a patch for the binutils project.
brgds, H-P
_______________________________________________
DejaGnu mailing list
DejaGnu@gnu.org
http://lists.gnu.org/mailman/listinfo/dejagnu
