Hello,
I just wanted to ask if we really want to bail out in configure if the
installed flex is not 2.5.4.
This stops everyone with f.e. Debian Sarge to install PHP 5.2 (if he has
installed flex on his system). The normal user will never need flex for
PHP's configure but it could be that he needs flex for other software.
With PHP 5.2 this has become an either or.
Greetings
Stefan
Hi,
Currently we have to bail out if a new flex is installed, because the new
flex versions simply die when parsing the flex skeleton bundled in the Zend
folder. Why this happens? because flex has suffered a lot of changes and
doesn't support the old skeletons.
So currently we are stuck with the old flex version. This problem is so
irritating to me, that I even have that in my TODO list. The new flex
already supports re-entrant parsers, so we could get rid of the bundled
skeleton plus all the engine hacks related with flex.
Nuno
----- Original Message -----
Hello,
I just wanted to ask if we really want to bail out in configure if the
installed flex is not 2.5.4.This stops everyone with f.e. Debian Sarge to install PHP 5.2 (if he has
installed flex on his system). The normal user will never need flex for
PHP's configure but it could be that he needs flex for other software.
With PHP 5.2 this has become an either or.Greetings
Stefan
Hi Nuno,
Currently we have to bail out if a new flex is installed, because the
new flex versions simply die when parsing the flex skeleton bundled in
the Zend folder. Why this happens? because flex has suffered a lot of
changes and doesn't support the old skeletons.
IMHO the correct way would be to warn the user about the incompatible
flex version (like we did before) and then internally make configure
believe that NO flex is installed. This should work, shouldn't it?
Otherwise we really have the problem that a normal user cannot install
PHP 5.2 anymore.
Stefan
Otherwise we really have the problem that a normal user cannot install
PHP 5.2 anymore.
Are you talking about CVS or snapshots here?
regards,
Derick
Otherwise we really have the problem that a normal user cannot install
PHP 5.2 anymore.Are you talking about CVS or snapshots here?
There have been a change in configure.in by ilia 4-5 weeks ago, that
changed the warning to a bailout. If you now compile a snapshot it will
bailout in configure because you have the wrong flex (although you don't
need it at all for a snapshot).
Stefan
Well actually it was a change to acinclude.m4
http://cvs.php.net/viewcvs.cgi/php-src/acinclude.m4?r1=1.332.2.14&r2=1.332.2.14.2.1
There is a debian package flex-old that supports the old functionality.
Just install that first.
Michael Gall wrote:
There is a debian package flex-old that supports the old functionality.
Just install that first.
That is besides Stefan's point. The snapshot and release tarballs come
with pre-generated scanners and parsers. Neither flex, nor re2c, nor
bison should be needed. Yet the configure script bails out if it finds
an incompatible version of one of these tools although the tool will not
be used during the "make".
--
Sebastian Bergmann http://www.sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69
I agree with Sebastian and Stefan. If its not "necessary" in order to
compile/use PHP for everyday users then it should throw a Warning and keep
on going. Joe Average might not know that flex, re2c or bison was installed
a dependancy for another service, etc.
-bok
Michael Gall wrote:
There is a debian package flex-old that supports the old functionality.
Just install that first.That is besides Stefan's point. The snapshot and release tarballs come
with pre-generated scanners and parsers. Neither flex, nor re2c, nor
bison should be needed. Yet the configure script bails out if it finds
an incompatible version of one of these tools although the tool will not
be used during the "make".--
Sebastian Bergmann http://www.sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69--
--
Xnyo - http://xnyo.odynia.org/