[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bison-1.29 test failures

From: Len Makin
Subject: bison-1.29 test failures
Date: Tue, 09 Oct 2001 16:08:23 +1000

The problem:
Building and installing on SunOS 5.5.1 Generic_103640-29 sun4u 
sparc SUNW,Ultra-2 gcc 2.95.2 have discovered a problem with your tests.
[The build also assumes a GNU make but this is easily fixed by using a "gmake"
The problem is that your tests "output.at" assume behaviour of sed to be 
that of GNU sed. We use Sun /usr/xpg4/bin/sed as POSIX compatible. This
produces e.g.
ls foo.c foo.h foo.output | sort | tr '\n' ' ' | /usr/xpg4/bin/sed 's/.$//g'
sed: Missing newline at end of file standard input.
foo.c foo.h foo.output

and the error message causes failure. Changing the path to use Sun /bin/sed
[or /usr/bin/sed /usr/5bin/sed /usr/ucb/sed] gives a null output e.g.

ls foo.c foo.h foo.output | sort | tr '\n' ' ' | /usr/ucb/sed 's/.$//g'

which also causes failure of all output.at tests.
However editing testsuite and substituting gsed for sed, gets a successful
test run (gmake check).

Solutions: Use configure to check for sed and gsed, and prefer gsed for use in
        Perhaps configure tests to check for a user-settable environment 
variable SED (default "sed") for use in testsuite.

or ... change the tests so they don't depend on GNU sed behaviour. ??? YMMV
At least you could document the dependency. ;-(
        Len Makin
address@hidden:+61 3 9669 8109: CSIRO/Bureau of Meteorology
      High Performance Computing and Communications Centre
24th floor, 150 Lonsdale St | GPO Box 1289K, Melbourne, VIC 3001 Australia

reply via email to

[Prev in Thread] Current Thread [Next in Thread]