headers
Philippe De Muyter | 3 Apr 11:56
Picon
Favicon

%left MOD 305 : parse error, unexpected "integer"

Hi bison-maintainers,

I try to use the current version of bison to compile qddb, a free software
package, on a current computer.  I had already compiled successfully, using
bison, the same qddb version on an older computer back in 1998 :)

The current version of bison fails, while the old one worked, on

	%left MOD 305

with :
	bison -dy /share/src/gnu/qddb-1.43p3/Lib/LibQddb/TableParse.y
	/share/src/gnu/qddb-1.43p3/Lib/LibQddb/TableParse.y:54.11-13: parse error, unexpected "integer"

Summary :
	bison 1.25 used to work
	bison 1.75 failed
	bison 2.3 fails

This seems like an old regression in bison

Thanks for reading so far

Philippe

--

-- 
Philippe De Muyter  phdm at macqel dot be  Tel +32 27029044
Macq Electronique SA  rue de l'Aeronef 2  B-1140 Bruxelles  Fax +32 27029077
(Continue reading)

Permalink | Reply | 3 comments |
headers
Joel E. Denny | 4 Apr 05:11

Re: %left MOD 305 : parse error, unexpected "integer"

On Thu, 3 Apr 2008, Philippe De Muyter wrote:

> The current version of bison fails, while the old one worked, on
> 
> 	%left MOD 305
> 
> with :
> 	bison -dy /share/src/gnu/qddb-1.43p3/Lib/LibQddb/TableParse.y
> 	/share/src/gnu/qddb-1.43p3/Lib/LibQddb/TableParse.y:54.11-13: parse error, unexpected "integer"

Thanks for the report.  This is fixed in CVS.
Permalink | Reply | 2 comments |
headers
Joel E. Denny | 4 Apr 06:52

Re: Bash vs. sh

On Wed, 26 Mar 2008, Paul Hilfinger wrote:

> The bootstrap file is headed
> 
>     #! /bin/sh
> 
> However, it contains lines such as 
> 
>      if ! "$SHA1SUM" -c --status "$cksum_file" < "$new_po" >  /dev/null; then
> 
> and 
> 
>      if ! test -d "$dst_dir"; then
> 
> In a standard Solaris 10 installation, /bin/sh does not recognize the
> '!' command.  I had to fix this by changing the shell used by
> bootstrap to /bin/bash.

Thanks for the report.  I don't know whether Bison should switch to 
/bin/bash or just weed out Bash-specific code.  This feels like a question 
for Paul Eggert.
Permalink | Reply | 0 comments |
headers
Philippe De Muyter | 4 Apr 10:13
Picon
Favicon

Re: %left MOD 305 : parse error, unexpected "integer"

Hi Joel,

On Thu, Apr 03, 2008 at 11:11:06PM -0400, Joel E. Denny wrote:
> On Thu, 3 Apr 2008, Philippe De Muyter wrote:
> 
> > The current version of bison fails, while the old one worked, on
> > 
> > 	%left MOD 305
> > 
> > with :
> > 	bison -dy /share/src/gnu/qddb-1.43p3/Lib/LibQddb/TableParse.y
> > 	/share/src/gnu/qddb-1.43p3/Lib/LibQddb/TableParse.y:54.11-13: parse error, unexpected "integer"
> 
> Thanks for the report.  This is fixed in CVS.

Thanks. Is there a snapshot version available somewhere ? I only found 2.3a
which is much older than the fix.

Philippe
Permalink | Reply | 1 comment |
headers
Joel E. Denny | 4 Apr 17:03

Re: %left MOD 305 : parse error, unexpected "integer"

On Fri, 4 Apr 2008, Philippe De Muyter wrote:

> > Thanks for the report.  This is fixed in CVS.
> 
> Thanks. Is there a snapshot version available somewhere ? I only found 2.3a
> which is much older than the fix.

Just CVS:

  http://savannah.gnu.org/cvs/?group=bison

We're hoping to release 2.3b soon.
Permalink | Reply | 0 comments |
headers
Alessandro Vincenzi | 17 Apr 19:29
Picon

Error in the documentation

Hi,

I'm an italian university student in computer science. I'm using bison in a
project and i've found a typing error in the documentation at section 2.4.2:

%preg -> %prec

in the uminus rule.

I know, it has no importance. Just for correctness.

All the best.

Alessandro Vincenzi
Permalink | Reply | 2 comments |
headers
Joel E. Denny | 18 Apr 01:16

Re: Error in the documentation

On Thu, 17 Apr 2008, Alessandro Vincenzi wrote:

> project and i've found a typing error in the documentation at section 2.4.2:
> 
> %preg -> %prec

Thanks.  This is fixed in CVS.
Permalink | Reply | 0 comments |
headers
Akim Demaille | 18 Apr 08:24
Picon
Picon
Picon
Gravatar

Re: Error in the documentation


Le 17 avr. 08 à 19:29, Alessandro Vincenzi a écrit :
> Hi,
>
> I'm an italian university student in computer science. I'm using  
> bison in a
> project and i've found a typing error in the documentation at  
> section 2.4.2:
>
> %preg -> %prec
>
> in the uminus rule.
>
> I know, it has no importance. Just for correctness.
>
> All the best.

Thank you Alessandro.  It has been recently fixed.
Permalink | Reply | 0 comments |
headers
Joel E. Denny | 21 Apr 02:36

Re: Difficulty trying to build distribution from CVS sources

On Sat, 16 Feb 2008, Joel E. Denny wrote:

> On Mon, 21 Jan 2008, Juan Manuel Guerrero wrote:
> 
> > At a first glance all steps appeared to work except for the one to build
> > the dist target.  That target produces the following output:
> > 
> >   make: build-aux/git-version-gen: Kommando nicht gefunden   (command not found)
> >   INFO: rerunning autoconf for new version string: 
> >   cat: .prev-version: Datei oder Verzeichnis nicht gefunden  (file or directory not found)
> >   /bin/sh ./config.status --recheck
> >   running CONFIG_SHELL=/bin/sh /bin/sh ./configure   --no-create --no-recursion
> > [snip]
> >   make: build-aux/git-version-gen: Kommando nicht gefunden
> >   INFO: rerunning autoconf for new version string: 
> >   cat: .prev-version: Datei oder Verzeichnis nicht gefunden
> >   /bin/sh ./config.status --recheck
> >   running CONFIG_SHELL=/bin/sh /bin/sh ./configure   --no-create --no-recursion
> > [snip]
> > 
> > As can be seen it is a infinite loop.  After inspecting bison/build-aux/ I have
> > seen that there is no git-version-gen
> 
> Juan, sorry for the very slow response.  I see the same infinite loop you 
> do.
> 
> Paul, the problem goes away when I check out Bison from 2007-09-21 right 
> before your changes to GNUmakefile but not after.  Could you look into 
> this?  Thanks.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Joel E. Denny | 21 Apr 03:27

Re: Bash vs. sh

Coreutils maintainers,

It appears that Bison's bootstrap script is occasionally sync'ed against 
Coreutils'.  Paul Hilfinger, one of the Bison developers, recently made 
the discovery quoted below, which I figure might also be relevant to 
Coreutils.

On Fri, 4 Apr 2008, Joel E. Denny wrote:

> On Wed, 26 Mar 2008, Paul Hilfinger wrote:
> 
> > The bootstrap file is headed
> > 
> >     #! /bin/sh
> > 
> > However, it contains lines such as 
> > 
> >      if ! "$SHA1SUM" -c --status "$cksum_file" < "$new_po" >  /dev/null; then
> > 
> > and 
> > 
> >      if ! test -d "$dst_dir"; then
> > 
> > In a standard Solaris 10 installation, /bin/sh does not recognize the
> > '!' command.  I had to fix this by changing the shell used by
> > bootstrap to /bin/bash.
> 
> Thanks for the report.  I don't know whether Bison should switch to 
> /bin/bash or just weed out Bash-specific code.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane