Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:1151 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 13954 invoked from network); 2 May 2003 06:17:41 -0000 Received: from unknown (HELO mail.kromann.info) (64.186.239.125) by pb1.pair.com with SMTP; 2 May 2003 06:17:41 -0000 Received: from Swwwing2000 (unknown [64.186.239.115]) by mail.kromann.info (Postfix) with SMTP id 40CC42AF58 for ; Thu, 1 May 2003 15:17:26 -0700 (PDT) To: internals@lists.php.net X-Mailer: Swwwing 2000 Message-ID: <10518563513960000@9866357972520000.9866341568840000> MIME-Version: 1.0 Reply-To: "Frank M. Kromann" Date: Thu, 01 May 2003 23:19:12 -0700 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Bison problems From: frank@kromann.info ("Frank M. Kromann") Hi Steph, Installing 1.75 under cygwin, in its own directory is no problem. It causes a few warnings in the ming extension, but works fine with PHP. 1.875b Works great on the min extension (ming sources from cvs), but the ini parser does not like the last line of the ini file. Everything else works fine. It must be fixable. I would like to test the version you are using. - Frank > 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" > To: > 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 > > > > > > > > > -- > > > PHP Internals - PHP Runtime Development Mailing List > > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > > > > > > > > -- > > PHP Internals - PHP Runtime Development Mailing List > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >