Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79586
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.45 as permitted sender)
MIME-Version: 1.0
Sender: julienpauli@gmail.com
In-Reply-To: <CAPwsocHT58-NFyp4XMuRu7AKtMxUCM-s8B--Cf0UJYWOR5hmaQ@mail.gmail.com>
References: <54894D5B.7070806@php.net> <CAPwsocHT58-NFyp4XMuRu7AKtMxUCM-s8B--Cf0UJYWOR5hmaQ@mail.gmail.com>
Date: Fri, 12 Dec 2014 09:47:43 +0100
Message-ID: <CAMUwpuQ7xRmAz1qUQZyY1ksBNCZj0onin_hS7G2EdL3TLV50-w@mail.gmail.com>
To: Leigh <leight@gmail.com>
Cc: Sebastian Bergmann <sebastian@php.net>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] bison 3.0
From: jpauli@php.net (Julien Pauli)

On Thu, Dec 11, 2014 at 2:36 PM, Leigh <leight@gmail.com> wrote:
> On 11 December 2014 at 07:52, Sebastian Bergmann <sebastian@php.net> wrote:
>>  Hi!
>>
>>  I just updated my notebook to Fedora 21 and am no longer able to
>>  build PHP on it since I now have bison 3.0.2 instead of bison 2.7.
>>
>>  bison 3.0 is blacklisted in Zend/acinclude.m4. Is bison 3.0
>>  incompatible with our parser specification? If so, will it be
>>  upgraded? It's not really a good situation to be incompatible
>>  with current versions of essential tools such as bison.
>>
>>  Best,
>> Sebastian
>>
>
> I've been building fine on a Debian based system with bison 3.0.2 just
> by commenting out the exclusion.
>
> There is also this: https://github.com/php/php-src/pull/685

In the worst scenario, there is also : downgrade your Bison.

That's what we do as RMs, to have a very accurate version of Bison
when we prepare the builds.
Bison is very easy to compile, and so to replace your default OS's one is easy.


Julien.P