[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bison 2.0 test suite on Mac OS X.3.8
From: |
Hans Aberg |
Subject: |
Re: Bison 2.0 test suite on Mac OS X.3.8 |
Date: |
Mon, 21 Mar 2005 20:48:11 +0100 |
At 11:00 -0800 2005/03/21, Paul Eggert wrote:
Hans Aberg <address@hidden> writes:
What are CC, CFLAGS, and CPPFLAGS set to on your host? That
might explain the problem.
Do you mind to help me a bit on this.
Try doing this:
cd tests
./testsuite -v -d 5
grep -E '(CC|CFLAGS|CPPFLAGS|LDFLAGS|abs_top_builddir)=' testsuite.log
Assuming the output looks something like this:
| abs_top_builddir='/some/long/path'
| CC='gcc'
| CFLAGS='-g -O2 '
| CPPFLAGS="-DHAVE_CONFIG_H=1 -I$abs_top_builddir "
| GCC='yes'
| LDFLAGS=''
then execute these commands:
abs_top_builddir='/some/long/path'
CC='gcc'
CFLAGS='-g -O2 '
CPPFLAGS="-DHAVE_CONFIG_H=1 -I$abs_top_builddir "
LDFLAGS=''
cd testsuite.dir/005
set -x
$CC $CFLAGS $CPPFLAGS -c input.c -o input.o
$CC $CFLAGS $CPPFLAGS -c main.c -o main.o
$CC $CFLAGS $CPPFLAGS $LDFLAGS input.o main.o $LIBS -o input
Please email to bison-bugs the output of all the above commands
(including the "grep").
It is a bit strange that maiking bison works, without those flags
then, but the test suite fails. How is it setup in the "make" of
Bison, as these falgs then are not needed?
"make check" can exercise features of the underlying system that
"make" and "make install" do not.
The output is as follows:
(set -x was inadvertently executed twice, but it should not make any
difference.)
Hans-Abergs-Computer:~/Development haberg$ cd bison-2.0/tests/
Hans-Abergs-Computer:~/Development/bison-2.0/tests haberg$ ./testsuite -v -d 5
## ------------------------- ##
## GNU Bison 2.0 test suite. ##
## ------------------------- ##
5. input.at:130: testing ...
input.at:136: bison input.y
input.at:266: bison -d -v -o input.c input.y
input.at:267: $CC $CFLAGS $CPPFLAGS -c input.c -o input.o
stderr:
gcc: cannot specify -o with -c or -S and multiple compilations
stdout:
input.at:267: exit code was 1, expected 0
5. input.at:130: FAILED (input.at:267)
## ------------- ##
## Test results. ##
## ------------- ##
ERROR: 1 test was run,
1 failed unexpectedly.
## -------------------------- ##
## testsuite.log was created. ##
## -------------------------- ##
Please send `testsuite.log' and all information you think might help:
To: <address@hidden>
Subject: [GNU Bison 2.0] testsuite: 5 failed
Hans-Abergs-Computer:~/Development/bison-2.0/tests haberg$ grep -E
'(CC|CFLAGS|CPPFLAGS|LDFLAGS|abs_top_builddir)=' testsuite.log
|
abs_top_builddir='/Users/haberg/HansAberg/Computer/Development/Bison:Flex/Bison
Compiler/bison-2.0/tests/../.'
| CC='gcc'
| CFLAGS='-g -O2 '
| CPPFLAGS="-DHAVE_CONFIG_H=1 -I$abs_top_builddir "
| GCC='yes'
| LDFLAGS=''
Hans-Abergs-Computer:~/Development/bison-2.0/tests haberg$
abs_top_builddir='/Users/haberg/HansAberg/Computer/Development/Bison:Flex/Bison
Compiler/bison-2.0/tests/../.'
Hans-Abergs-Computer:~/Development/bison-2.0/tests haberg$ CC='gcc'
Hans-Abergs-Computer:~/Development/bison-2.0/tests haberg$ CFLAGS='-g -O2 '
Hans-Abergs-Computer:~/Development/bison-2.0/tests haberg$
CPPFLAGS="-DHAVE_CONFIG_H=1 -I$abs_top_builddir "
Hans-Abergs-Computer:~/Development/bison-2.0/tests haberg$ GCC='yes'
Hans-Abergs-Computer:~/Development/bison-2.0/tests haberg$ LDFLAGS=''
Hans-Abergs-Computer:~/Development/bison-2.0/tests haberg$ cd testsuite.dir/005
Hans-Abergs-Computer:~/Development/bison-2.0/tests/testsuite.dir/005
haberg$ set -x
Hans-Abergs-Computer:~/Development/bison-2.0/tests/testsuite.dir/005
haberg$ set -x
+ set -x
Hans-Abergs-Computer:~/Development/bison-2.0/tests/testsuite.dir/005
haberg$ $CC $CFLAGS $CPPFLAGS -c input.c -o input.o
+ gcc -g -O2 -DHAVE_CONFIG_H=1
-I/Users/haberg/HansAberg/Computer/Development/Bison:Flex/Bison
Compiler/bison-2.0/tests/../. -c input.c -o input.o
gcc: cannot specify -o with -c or -S and multiple compilations
Hans-Abergs-Computer:~/Development/bison-2.0/tests/testsuite.dir/005
haberg$ $CC $CFLAGS $CPPFLAGS -c main.c -o main.o
+ gcc -g -O2 -DHAVE_CONFIG_H=1
-I/Users/haberg/HansAberg/Computer/Development/Bison:Flex/Bison
Compiler/bison-2.0/tests/../. -c main.c -o main.o
gcc: cannot specify -o with -c or -S and multiple compilations
Hans-Abergs-Computer:~/Development/bison-2.0/tests/testsuite.dir/005
haberg$ $CC $CFLAGS $CPPFLAGS $LDFLAGS input.o main.o $LIBS -o input
+ gcc -g -O2 -DHAVE_CONFIG_H=1
-I/Users/haberg/HansAberg/Computer/Development/Bison:Flex/Bison
Compiler/bison-2.0/tests/../. input.o main.o -o input
gcc: Compiler/bison-2.0/tests/../.: No such file or directory
gcc: input.o: No such file or directory
gcc: main.o: No such file or directory
gcc: no input files
Hans-Abergs-Computer:~/Development/bison-2.0/tests/testsuite.dir/005 haberg$
--
Hans Aberg
- Bison 2.0 test suite on Mac OS X.3.8, Hans Aberg, 2005/03/20
- Re: Bison 2.0 test suite on Mac OS X.3.8, Hans Aberg, 2005/03/20
- Re: Bison 2.0 test suite on Mac OS X.3.8, Paul Eggert, 2005/03/21
- Re: Bison 2.0 test suite on Mac OS X.3.8, Hans Aberg, 2005/03/21
- Re: Bison 2.0 test suite on Mac OS X.3.8, Paul Eggert, 2005/03/21
- Re: Bison 2.0 test suite on Mac OS X.3.8,
Hans Aberg <=
- Re: Bison 2.0 test suite on Mac OS X.3.8, Paul Eggert, 2005/03/21
- Re: Bison 2.0 test suite on Mac OS X.3.8, Hans Aberg, 2005/03/22
- Autoconf patch to catch problems with spaces etc. in file names, Paul Eggert, 2005/03/22
- Re: Autoconf patch to catch problems with spaces etc. in file names, Hans Aberg, 2005/03/23
Re: Bison 2.0 test suite on Mac OS X.3.8, Hans Aberg, 2005/03/21