ID:               37462
 Updated by:       [EMAIL PROTECTED]
 Reported By:      ionut dot aivanesei at amdocs dot com
-Status:           Open
+Status:           Closed
 Bug Type:         Compile Failure
 Operating System: AIX 5.3
 PHP Version:      5.2.0


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

[2007-02-15 09:42:44] rainer dot tammer at schulergroup dot com

Hello,
I have a other solution to the nm problem ...
I changed the configure script.

I changed the nm relevant sed command:
  sed 's/\([A-Za-z0-9_]*\)\.o/\1.o/g' 
to
  sed 's/\([A-Za-z0-9_]*\)\.o/.libs\/\1.o/g'
.

As a result the nm no longer complains about the "0654-200 Cannot open
the specified file.".

Bye
  Rainer

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

[2007-01-19 20:15:36] lobster2 at xs4all dot nl

Problem (3) reported [19 Oct 2006 11:37pm UTC] sharanu_mudgal at yahoo
dot com

Only important if you need the php CLI executable.

Worked around this by symlinking all .libs/*.o one dir higher up the
hierarchy, where the .lo files with the same name reside.

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

[2006-06-22 16:43:56] burlybutler at hotmail dot com

I've found this bug too when compiling on the AIX platform. When doing
the 'make' it just prints out a spurious line (echo '\), so no
sapi/cli/php executable was made

As reported above, the problem can be worked around by using the
default BUILD_CLI option in the configure script, which was fine. Either
edit configure to disable the aix option, or put the default one
directly in the Makefile (remove backslashes).

Perhaps the AIX BUILD_CLI option works/worked on some versions (or its
something to do with shells) - must have been put there for a reason...

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

[2006-06-14 17:44:19] [EMAIL PROTECTED]

And make sure you have GNU tools in use, like GNU sed..

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

[2006-06-14 17:43:25] [EMAIL PROTECTED]

Try this configure line:

# ./configure --disable-all

Does it work then? And what kind of paths are [...] anyway?

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

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/37462

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

Reply via email to