PHP compile error

[kHz]

I am running AIX 5.1 ML9 and have tried compiling php 4.3.8, and 5.1.2 and I always get the same error. I have seen it on a bug list for php but it was supposedly fixed. Has anyone been able to compile PHP using 'configure --with-apxs2=/usr/local/apache2/bin/apxs' successfully?

# make install
echo '\
\
Installing PHP SAPI module: apache2handler
/usr/local/apache2/build/instdso.sh SH_LIBTOOL='/usr/local/apache2/build/libtool' libphp5.la /usr/local/apache2/modules
rm -f /usr/local/apache2/modules/libphp5.so
/usr/local/apache2/build/libtool --mode=install cp libphp5.la /usr/local/apache2/modules/
cp .libs/libphp5.a /usr/local/apache2/modules/libphp5.a
cp .libs/libphp5.lai /usr/local/apache2/modules/libphp5.la
libtool: install: warning: remember to run `libtool --finish /tmp/dl/php-5.1.2/libs'
chmod 755 /usr/local/apache2/modules/libphp5.so
chmod: /usr/local/apache2/modules/libphp5.so: A file or directory in the path name does not exist.
apxs:Error: Command failed with rc=65536
.
make: 1254-004 The error code from the last command is 1.


Stop.

 

[fletchsod]

I have that problem. Turned out there are 2 different problem.

You see, the echo shouldn't be spitting out the '\ \' stuffs and it should be spitting out wording instead. I don't remember what it is, so you'll have to hack into it yourself. It's not a PHP issue, but something with AIX. Something got lost along the way via AIX. I haven't finish debugging that part yet because I'm dealing with other problems first.

The 2nd problem I noticed you didn't have one which is a good thing. The instdso.sh shell script give a sed parse error in my case. So, the PHP's DSO module isn't put into Apache's directory.

 

[kHz]

Thanks. At least I'm not the only one. I did have the sed parse error, but like you, I don't remember what I did to fix that problem.

The build is successful, it is during the install where I get that apxs error that I can't figure out. On a php faq I saw to change three lines in *some script* if you get the error I am getting. Changing those lines didn't make any difference. I also say to change 'build_libtool_libs=yes' in the libtool script, but that also didn't work.

I am still wanting to fix it and get it working, but have other things to do first.

 

[fletchsod]

Yea, I had it working on my own with some hacking while the original problem still isn't fixed. Then one of the developer need to recompile PHP so one of hte database software would start working with PHP and it destroyed the PHP's DSO module. :-( It became obvious that it had to be fixed so I'm looking into seeing if I can get the AIX bugs fixed before anyone can be freely compile PHP without messing up.

>I am still wanting to fix it and get it working, but
>have other things to do first.
Me too.

 

[fletchsod]

Yea!! Someone found a fix to the Sed parse error today. I'm enclosing a copy of the patch..

--snip--
--- httpd-2.2.0/build/instdso.sh.org 2005-06-09 00:37:55.000000000 +0900
+++ httpd-2.2.0/build/instdso.sh 2006-03-02 18:11:32.372591000 +0900
@@ -61,8 +61,8 @@
exit 0
fi

-DLNAME=`sed -n "/^dlname=/{s/.*='\([^']*\)'/\1/;p}" $TARGETDIR/$DSOARCHIVE_BASENAME`
-LIBRARY_NAMES=`sed -n "/^library_names/{s/library_names='\([^']*\)'/\1/;p}" $TARGETDIR/$DSOARCHIVE_BASENAME`
+DLNAME=`sed -n "/^dlname=/{s/.*='\([^']*\)'/\1/;p;}" $TARGETDIR/$DSOARCHIVE_BASENAME`
+LIBRARY_NAMES=`sed -n "/^library_names/{s/library_names='\([^']*\)'/\1/;p;}" $TARGETDIR/$DSOARCHIVE_BASENAME`
LIBRARY_NAMES=`echo $LIBRARY_NAMES | sed -e "s/ *$DLNAME//g"`

if test -z "$DLNAME"
--snip--

The only thing different is by adding the ";" after the letter "p" in the sed script...

Now I get a new problem which is the same problem you got. Now, we onto something here... See my bug report at

http://issues.apache.org/bugzilla/show_bug.cgi?id=38108

Please help to get this bug fix so everyone can go to the next step but please do not spam the bugzilla. I'm serious about that spamming issues.

 

[fletchsod]

kHz - My comment isn't meant for you about bug fixing, it is meant for everybody who read this posting. So, sorry about the misunderstanding.