php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #40176 Bug #40038 gcc configure failure can be fixed with CXX=xlC ./configure
Submitted: 2007-01-19 20:05 UTC Modified: 2007-01-19 20:29 UTC
From: lobster2 at xs4all dot nl Assigned:
Status: Not a bug Package: *General Issues
PHP Version: 5.2.0 OS: AIX 5.2
Private report: No CVE-ID: None
View Developer Edit
 [2007-01-19 20:05 UTC] lobster2 at xs4all dot nl 
Description:
------------
The bug in configure for PHP 5.2.0 where it thinks gcc is the only compiler present (where it isn't), see bug #40038 can be fixed by issuing the following configure:

   $ CXX=xlC ./configure



Reproduce code:
---------------
Sorry not to include code because I do not have it at my disposal right now.

Expected result:
----------------
Why are these things written off as non-PHP bugs? Aren't the build and configure scripts not as much part of PHP as the code itself. Every time I build PHP on AIX I need to spend a few hours hunting "bugs" before it builds, whereas Linux/gcc compiles flawlessly.

I saw that the bug on the enum values has already been reported (fix: EXTRA_CFLAGS='-qenum=intlong' make).

Dito for compile syntax error on the // NULL comment that should have been /* NULL */ or something of the kind.

Another major pain was the location of .o files in the .libs subdirs instead of in the same dir as the .lo files reside and where nm expects them, causing the make of sapi/cli/php to fail. Adding symlinks solved this for me. See the Makefile where the output of the echo of .lo files to sed is fed to nm.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2007-01-19 20:14 UTC] tony2001@php.net 
Sorry, but your problem does not imply a bug in PHP itself.  For a
list of more appropriate places to ask for help using PHP, please
visit http://www.php.net/support.php as this bug system is not the
appropriate forum for asking support questions.  Due to the volume
of reports we can not explain in detail here why your report is not
a bug.  The support channels will be able to provide an explanation
for you.

Thank you for your interest in PHP.
 [2007-01-19 20:29 UTC] lobster2 at xs4all dot nl 
Why was this report set to status Bogus within a few minutes? The problems and *fixes* I submitted are very real. This is demoralizing :-(
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Sat Dec 06 23:00:01 2025 UTC