Bug #64461 [Com]: Zend/zend_language_parser.h error with --enable-maintainer-zts in tarballs
Edit report at https://bugs.php.net/bug.php?id=64461&edit=1
ID: 64461
Comment by: remi@php.net
Reported by: kevin dot waterson at gmail dot com
Summary: Zend/zend_language_parser.h error with
--enable-maintainer-zts in tarballs
Status: Re-Opened
Type: Bug
Package: Compile Failure
Operating System: Centos 6.3
PHP Version: 5.5.0beta1
Block user comment: N
Private report: N
New Comment:
5.5.0beta1 parser is generated with bison 2.6.1
snapshot parser is generated with bison 2.4.1
And snapshot works.
Previous Comments:
------------------------------------------------------------------------
[2013-03-22 00:32:05] aharvey@php.net
The tarball version of Zend/zend_language_parser.h has the following extra
declarations (at the end of the file, just before the last #endif) compared to
the generated version in my git checkout:
#ifdef YYPARSE_PARAM
#if defined __STDC__ || defined __cplusplus
int zendparse (void *YYPARSE_PARAM);
#else
int zendparse ();
#endif
#else /* ! YYPARSE_PARAM */
#if defined __STDC__ || defined __cplusplus
int zendparse (void);
#else
int zendparse ();
#endif
#endif /* ! YYPARSE_PARAM */
------------------------------------------------------------------------
[2013-03-22 00:29:58] aharvey@php.net
Mea culpa; I should have dug into this a little more. I can now reproduce this
with beta 1, after seeing another report on IRC.
Short version: configuring tarball builds with --enable-maintainer-zts results in
the error in the original report. I can't reproduce this if I run buildconf
myself in a Git tree, so it's something peculiar to the distributed tarballs.
------------------------------------------------------------------------
[2013-03-20 23:16:46] sixd@php.net
Closing as per previous comment
------------------------------------------------------------------------
[2013-03-20 23:11:11] kevin dot waterson at gmail dot com
OK! Fixed in latest snap. Thanks for looking
Kev
------------------------------------------------------------------------
[2013-03-20 20:20:16] aharvey@php.net
I don't seem to be able to reproduce this. So, a few questions for you:
1. How did you get PHP? Tarball, git checkout, something else?
2. Does the error still occur with a blank configure line (ie just ./configure)?
3. Does it still happen with the latest 5.5 snapshot from http://snaps.php.net/?
------------------------------------------------------------------------
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
https://bugs.php.net/bug.php?id=64461
--
Edit this bug report at https://bugs.php.net/bug.php?id=64461&edit=1
Thread (8 messages)