[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: |
Sun, 20 Mar 2005 16:00:47 +0100 |
Here is the log from test suite 5, which failed:
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: 5. Torturing the Scanner (input.at:130): FAILED (input.at:267)
Looking at some of the other test suite errors, they seem to be the
same from GCC. But I do not see why it happens.
--
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 <=
- 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, 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, 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