#17135: wine and wine-devel don't build with bison 2.4 installed -------------------------------------+-------------------------------------- Reporter: ryandesign@macports.org | Owner: ryandesign@macports.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: | Port: wine, wine-devel -------------------------------------+-------------------------------------- I didn't realize until now, but Wine uses bison during the build process. The wine/wine-devel ports don't declare a dependency on the bison port, but if the bison port is installed, it will be used. And bison 2.4 made a significant backward-incompatible change w.r.t. bison 2.3 which Wine doesn't like. For example wine-devel 1.1.8 says: {{{ /usr/bin/gcc-4.0 -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after- statement -Wwrite-strings -Wpointer-arith -I/mp/include -O2 -o parser.tab.o parser.tab.c parser.y: In function 'parser_parse': parser.y:320: error: parse error before '}' token make[2]: *** [parser.tab.o] Error 1 make[1]: *** [jscript] Error 2 make: *** [dlls] Error 2 }}} As a quick workaround, try using the system bison instead like libidl did in r41581. Then report the problem to the Wine developers. Use the bison23 port when available (#17113), until Wine is fixed upstream. -- Ticket URL: <http://trac.macports.org/ticket/17135> MacPorts <http://www.macports.org/> Ports system for Mac OS