[GiNaC-list] Parser problems once again (bad version of bison)

Sheplyakov Alexei varg at theor.jinr.ru
Tue Jan 30 13:38:02 CET 2007


On Mon, Jan 29, 2007 at 10:58:14PM -0500, David Fang wrote:
> 	I just build cln-1.1.13, ginac-1.3.6 myself (OS X 10.4, dual G4)
> without problems, and bison didn't even play a role because ginac ships
> the resulting .cc sources with it (pre-built using bison 1.875, it seems).
Ouch! This version of bison is known to generate bad code, see 
for more details. Thus all gcc 4.1 users (read: all more or less up-to-date
GNU/Linux distros users) will hit parser error bug again. :( In fact
we've already had such a bug report,

I thought that was Fedora-specific issue, but apparently official
version 1.3.6 fails too (to be more specific, make check fails due to
parser errors). Removing input_parser.cc (so it will be regenerated
with bison version 2.3) and recompiling solves the problem. I did not
notice it earlier since I use git version
(so input_{parser,lexer}.cc generated at compile time).

Just in a case,
$ g++ --version | head -n 1
g++ (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
$ bison --version | head -n 1
bison (GNU Bison) 2.3

I propose to make new bugfix-only release (e.g. regenerate
input_parser.cc with "known-good" bison version)...

Best regards,

All science is either physics or stamp collecting.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: Digital signature
Url : http://www.cebix.net/pipermail/ginac-list/attachments/20070130/96043000/attachment.pgp

More information about the GiNaC-list mailing list