Bison problems View as Markdown

Frank M. Kromann wrote:

I'm not using buildconf on Win32. I'm only using bison/flex from
cygwin everything else is done with Visual Studio.

http://www.sebastian-bergmann.de/blog/archives/e_40.html :-)

--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/

Did I help you? Consider a gift: http://wishlist.sebastian-bergmann.de/

At 21:36 01.05.2003, Frank M. Kromann wrote:

I'm not using buildconf on Win32. I'm only using bison/flex from cygwin
everything else is done with Visual Studio.

oh nice!

1.75 is the last version known to be working

Frank, I forgot to tell you I found a native win32 bison that isn't
pre-determined-path-dependant.. (1.28 afair)

One of those things on the TODO.

(yeah OK Edin, after Amsterdam!)

----- Original Message -----
From: "Frank M. Kromann" frank@kromann.info
To: internals@lists.php.net
Sent: Thursday, May 01, 2003 7:36 PM
Subject: Re: [PHP-DEV] Bison problems

I'm not using buildconf on Win32. I'm only using bison/flex from
cygwin
everything else is done with Visual Studio.

• Frank

At 21:17 01.05.2003, Frank M. Kromann wrote:

Hi,

After upgrading to bison 1.875b (on win32 with CygWin) I have
problems
with the ini parser. It reports a parse error on the last line of
the
ini
file. Even if that line is empty.

The error report is printed to stdout, so is shows up on evry page
generated :-)

Installing and using bison 1.75 resolves the problem.

Is this a known problem, and is there a way to fix it other than
using
the
older version of bison ?

YES lookup your buildconf output.

regards
marcus