Ryan Schmidt <[EMAIL PROTECTED]> writes:
>
> On Nov 6, 2008, at 07:40, [EMAIL PROTECTED] wrote:
>
> > Revision: 41581
> > http://trac.macports.org/changeset/41581
> > Author: [EMAIL PROTECTED]
> > Date: 2008-11-06 05:40:00 -0800 (Thu, 06 Nov 2008)
> > Log Message:
> > -----------
> > libidl: use system bison since MacPorts bison 2.4 (#41450) does not
> > work
>
> Could you elaborate how MacPorts bison 2.4 does not work for you? I'm
> having trouble with it too, for pure-devel [1], but using the system
> bison is not an option for me as I need at least version 2.1a and
> Tiger provides version 1.28.
>
The libidl Makefile calls
bison -y -d -v 2>/dev/null ./parser.y
The MacPorts version of bison is called, and an error ensues:
/opt/local/bin/bison -y -d -v ./parser.y
./parser.y:610.9-10:
$$ for the midrule at $6 of `struct_type' has no declared type
./parser.y:627.9-10: $$
for the midrule at $10 of `union_type' has no declared type
The Leopard version of bison gives innocuous looking warnings:
/usr/bin/bison -y -d -v ./parser.y
./parser.y:606.25-618.1: warning: unused value: $3
./parser.y:621.25-635.1: warning: unused value: $3
./parser.y:716.25-732.1: warning: unused value: $4
./parser.y:780.25-781.68: warning: unused value: $1
./parser.y:811.25-818.1: warning: unused value: $3
./parser.y:926.25-933.1: warning: unused value: $3
Unfortunately, I know very little about Bison and Yacc, so the quickest fix
seemed to be to simply call the system bison.
This was not needed a few days ago, so it seems to be a result of the upgrade
of bison 2.3 -> 2.4.
I know it is a really bad idea, but if Bison 2.4 is a significant change that is
causing problems with several ports, we could always create a bison-compat
port which would remain at version 2.3.
-Marcus
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
