Compilation failure on AIX with 5.1.4

php.internals

Mark Spruiell

20 years ago
Building PHP 5.1.4 on AIX fails in two places with a syntax error: Zend/zend_language_parser.c:2585 Zend/zend_ini_parser.c:1081 The offending code is the same in both cases, which is not surprising since they are both bison-generated files: #if defined (__STDC__) || defined (__cplusplus) int yyparse (void) #else int yyparse () ; #endif The compilation succeeds after I delete the line containing the semicolon. I downloaded a 5.2 snapshot and verified that this line is still present. Cheers, - Mark

Antony Dovgal

20 years ago
On 07.06.2006 22:53, Mark Spruiell wrote:
> Building PHP 5.1.4 on AIX fails in two places with a syntax error: > > Zend/zend_language_parser.c:2585 > Zend/zend_ini_parser.c:1081 > > The offending code is the same in both cases, which is not surprising > since they are both bison-generated files: > > #if defined (__STDC__) || defined (__cplusplus) > int > yyparse (void) > #else > int > yyparse () > ; > #endif > > The compilation succeeds after I delete the line containing the > semicolon. > > I downloaded a 5.2 snapshot and verified that this line is still > present.
Do you have a patch?
-- Wbr, Antony Dovgal

Antony Dovgal

20 years ago
On 08.06.2006 01:56, Antony Dovgal wrote:
> On 07.06.2006 22:53, Mark Spruiell wrote: >> Building PHP 5.1.4 on AIX fails in two places with a syntax error: >> >> Zend/zend_language_parser.c:2585 >> Zend/zend_ini_parser.c:1081 >> >> The offending code is the same in both cases, which is not surprising >> since they are both bison-generated files: >> >> #if defined (__STDC__) || defined (__cplusplus) >> int >> yyparse (void) >> #else >> int >> yyparse () >> ; >> #endif >> >> The compilation succeeds after I delete the line containing the >> semicolon. >> >> I downloaded a 5.2 snapshot and verified that this line is still >> present. > > Do you have a patch?
And yes, I forgot to add that: it works perfectly fine here, on AIX 5.3.
-- Wbr, Antony Dovgal

Mark Spruiell

20 years ago
On 08.06.2006 01:56, Antony Dovgal wrote:
> Do you have a patch?
I was a bit concerned about the fact that these are bison-generated files. Doesn't that imply a bug in whatever version of bison was used to generate these files? And wouldn't the bug instantly reappear as soon as these files are regenerated for whatever reason?
> And yes, I forgot to add that: it works perfectly fine here, on AIX 5.3.
Perhaps it's a difference in our compilers. I'm using IBM's VisualAge C compiler. Take care, - Mark

Antony Dovgal

20 years ago
On 08.06.2006 01:13, Mark Spruiell wrote:
> On 08.06.2006 01:56, Antony Dovgal wrote: > >> Do you have a patch? > > I was a bit concerned about the fact that these are > bison-generated files. Doesn't that imply a bug in > whatever version of bison was used to generate these > files? And wouldn't the bug instantly reappear as soon > as these files are regenerated for whatever reason?
Well, your second phrase is the answer for this question.
>> And yes, I forgot to add that: it works perfectly fine here, on AIX 5.3. > > Perhaps it's a difference in our compilers. I'm using IBM's > VisualAge C compiler.
-- Wbr, Antony Dovgal