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
On Thu, Dec 11, 2014 at 8:52 AM, 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--
CCing Mike as he was the author who originally added 3.0 to the exclude
list.
I have a vague memory of building master successfully with bison 3.0.2
(from homebrew) on Mac Mavericks via removing 3.0 from
bison_version_exclude in Zend/acinclude.m4 so I think that not all versions
of bison 3.0 are affected, but currently I'm using the bison27
alternative(as XCode/Command Line Tools comes with bison 2.3 by default and
master requires >=2.4).
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
AFAIK, PHP builds fine with bison 3. At least with the common scenarios on
UNIX like systems.
TS builds might be the problem if my memory serves me right.
Kaplan
On Thu, Dec 11, 2014 at 8:52 AM, 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--
CCing Mike as he was the author who originally added 3.0 to the exclude
list.
I have a vague memory of building master successfully with bison 3.0.2
(from homebrew) on Mac Mavericks via removing 3.0 from
bison_version_exclude in Zend/acinclude.m4 so I think that not all versions
of bison 3.0 are affected, but currently I'm using the bison27
alternative(as XCode/Command Line Tools comes with bison 2.3 by default and
master requires >=2.4).--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
CCing Mike as he was the author who originally added 3.0 to the exclude
list.
Yes, I'm on ArchLinux, which has very recent software versions, so I
just added it to the exclude, when I upgraded bison to 3.0 and then
downgraded bison again.
IIRC ZTS builds fail with bison3 because of removed features, which were
already deprecated in 2.7.
--
Regards,
Mike
Michael Wallner in php.internals (Fri, 12 Dec 2014 12:02:53 +0100):
CCing Mike as he was the author who originally added 3.0 to the exclude
list.Yes, I'm on ArchLinux, which has very recent software versions, so I
just added it to the exclude, when I upgraded bison to 3.0 and then
downgraded bison again.IIRC ZTS builds fail with bison3 because of removed features, which were
already deprecated in 2.7.
On Windows Bison 3 creates wrong versions of zend_ini_parser.c and
zend_language_parser.c, but only for PHP 5.4 ZTS.
Jan
Michael Wallner in php.internals (Fri, 12 Dec 2014 12:02:53 +0100):
CCing Mike as he was the author who originally added 3.0 to the exclude
list.Yes, I'm on ArchLinux, which has very recent software versions, so I
just added it to the exclude, when I upgraded bison to 3.0 and then
downgraded bison again.IIRC ZTS builds fail with bison3 because of removed features, which were
already deprecated in 2.7.On Windows Bison 3 creates wrong versions of zend_ini_parser.c and
zend_language_parser.c, but only for PHP 5.4 ZTS.
The bison blacklist check was introduced with PHP-5.6.
for 5.4 and 5.5 we have the old whitelist and for 5.4 the maximum supported
bison version listed there is 2.6.4.
Sebastian, could you clarify which PHP versions do you feel necessary to
support bison 3 with it?
I think that 5.4 is out of question, having it in 5.5 would be nice, but
not really mandatory, as most distros will still provide legacy bison
packges before 5.5 is eoled.
(Fedora 20 had bison 2.7, fedora 21 has bison 3.0.2 but fc21 already ships
with php 5.6).
What do you think?
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
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
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,
SebastianI'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
Am 12.12.2014 um 09:47 schrieb Julien Pauli:
In the worst scenario, there is also: downgrade your Bison.
I have done that for now, of course. What worries me is the reliance
on outdated and unsupported tools.