ID:               30774
 Updated by:       [EMAIL PROTECTED]
 Reported By:      creinig at sunsite dot dk
-Status:           Feedback
+Status:           Bogus
 Bug Type:         Compile Failure
 Operating System: Debian/Sarge
 PHP Version:      4.3.9
 New Comment:

This has nothing to do with bison, but flex. PHP only works with 2.5.4
and not with 2.5.31, this is not a bug.


Previous Comments:
------------------------------------------------------------------------

[2004-11-13 20:43:03] [EMAIL PROTECTED]

Please try bison 1.28, 1.35, or 1.75, as PHP supports only these
versions.

------------------------------------------------------------------------

[2004-11-13 20:38:55] creinig at sunsite dot dk

$ bison --version 
bison (GNU Bison) 1.875a

------------------------------------------------------------------------

[2004-11-13 20:15:06] [EMAIL PROTECTED]

What version of bison do you have ?

------------------------------------------------------------------------

[2004-11-13 20:10:15] creinig at sunsite dot dk

Played a bit more with the php-5.0.2 build. The first 2 
"make" calls after doing a "rm -r *" in the separate build 
dir and calling configure yield the flex error, from the 
third try on it continues to the missing libfcgi dir. 
(tried this sequence twice now, with identical behavior 
each time)

------------------------------------------------------------------------

[2004-11-13 20:01:51] creinig at sunsite dot dk

Tried with php-5.0.2. On the first and second tries I got 
the same flex internal error in Zend/zend_ini_scanner.c as 
with the php4 snapshot (just with 4 shift/reduce mentioned 
instead of 2). 
 
Third try (after redirecting make stdout to a file) it 
skipped that error and continued until stopping at this: 
 
FATAL: can't create sapi/cgi/libfcgi/fcgi_stdio.o: No such 
file or directory 
make: *** [sapi/cgi/libfcgi/fcgi_stdio.lo] Error 1 
 
sapi/cgi/ is an empty dir at that place. 
 
"make clean ; make" repeats that error 
 
 
I realize that these are probably all independent build 
errors and thus should be separated into several bug 
reports. But that's IMHO better decided by someone familiar 
with the beast. In any case someone should have a *really* 
close look at the PHP build process, as it seems to be 
broken in several places.

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/30774

-- 
Edit this bug report at http://bugs.php.net/?id=30774&edit=1

Reply via email to