Message-ID: <3486256F.7040@binghamton.edu>
Date: Wed, 03 Dec 1997 19:37:19 -0800
From: Bob Kematick <kmatick AT binghamton DOT edu>
Reply-To: kmatick AT binghamton DOT edu
Organization: Binghamton University
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Bison & making f2c with v2.01 ??
References: <Pine DOT SOL DOT 3 DOT 91 DOT 971203141750 DOT 1584H-100000 AT sun45 DOT thp DOT Uni-Koeln DOT DE>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: bing11.net107.binghamton.edu
Lines: 29
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Wolfram Brenig wrote:
> 
> Hi,
> 
> I have a total (bison-)ignorants problem compiling f2c under v2.01:
> 
> In line 38 of the makefile which comes with the f2c95201 version
> in directory CONTRIB/F2C95201/SRC/SRC/MAKEFILE (distrib. with v1.xx
> and I'm not aware of more recent ones) invokes bison with
> 
> $(YACC) $(YFLAGS) gram
> 
> in v1.xx or v2.00 this line produced 4 harmless (?) shift/reduce conflict
> *warnings*, however, with a nicely working f2c.exe in your bin-directory
> at the end of the day.
> 
> Unfortunately, using v2.01 (instead of v1.xx or v2.00) bison
> jumps at me in this very line, now claiming the former warnings
> are suddenly 'type clash *errors*' and stops the make.
> 

A problem with bison 1.25 , these errors cause make to abort.
Previous bison versions ( eg 1.24) trated thes as warnings.

See if bison 1.24 is still in the djgpp archives at simtelnet.

An alternative , manually extract the first 100 lines from gram.c
and save to tokdefs.h , then edit the makefile so that it does
not try to regenerate gram.c using bison etc.