This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc 3.0 and Bison Version
- To: Mark Klein <mklein at dis dot com>
- Subject: Re: gcc 3.0 and Bison Version
- From: Fergus Henderson <fjh at cs dot mu dot oz dot au>
- Date: Thu, 10 May 2001 03:27:03 +1000
- Cc: gcc at gcc dot gnu dot org
- References: <4.2.0.58.20010509094652.03b63d68@garfield.dis.com>
On 09-May-2001, Mark Klein <mklein@dis.com> wrote:
> I just refreshed my workspace from cvs and tried a build of 3.0
> and got the following:
>
> make[1]: Leaving directory `/DIS/GNU/src/egcs-3.0/obj-MPE/gcc/po'
> echo "int xxy_us_dummy;" >tmp-dum.c
> ./xgcc -B./ -B/usr/local/hppa1.0-hp-mpeix/bin/ -isystem
> /usr/local/hppa1.0-hp-mp
> eix/include -S tmp-dum.c
> cc1: tmp-dum.c: Invalid argument
> cc1: tmp-dum.c: Invalid argument
> Errors detected in input file (your bison.simple is out of date)
> make: *** [s-under] Error 1
> /DIS/GNU/src/egcs-3.0/obj-MPE/gcc(205): bison --version
> bison (GNU Bison) 1.28a
>
> Copyright 1984, 1986, 1989, 1992, 2000, 2001 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> /DIS/GNU/src/egcs-3.0/obj-MPE/gcc(206):
>
> Does 3.0 need a different version of Bison?
The error message here about bison.simple is misleading.
It occurs when yyparse() fails but errorcount == 0.
In this case the reason that yyparse() is failing probably
has something to do with the "cc1: tmp-dum.c: invalid argument"
error messages, rather than the version of Bison being out of date.
--
Fergus Henderson <fjh@cs.mu.oz.au> | "I have always known that the pursuit
| of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh> | -- the last words of T. S. Garp.