ID: 11716 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: No Feedback +Status: Closed Bug Type: Apache related Operating System: AIX 4.3.3 PHP Version: 4.2.2 New Comment:
I've tested using CVS snapshots. But there is still a installation problem what I mentioned on 30 July. I think it is a bug of libtool generated from PHP configure script. I know this is a different problem from 'segmentation fault', what I submitted first. So I'd like to close this case. -- CheolMin Lee Previous Comments: ------------------------------------------------------------------------ [2002-11-21 17:07:49] [EMAIL PROTECTED] No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. ------------------------------------------------------------------------ [2002-11-10 18:48:56] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php4-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-latest.zip ------------------------------------------------------------------------ [2002-08-17 01:57:03] [EMAIL PROTECTED] Part of the reason we ask to try new versions is a developer may believe they have fixed the bug. Not many of us have access to an AIX box for any testing. The patch provided though for fixing this is a great help. The biggiest problem with it is, it's been created for the configure script which is a generated file. If you can port it to the ltmain.sh and/or the acinclude.m4 (which ever requires the work) that would ensure its inclusion in the next release of PHP. But right now I can only seem to make 1/2 of it work. Message sent to PHP Dev asking for more help ------------------------------------------------------------------------ [2002-07-30 09:02:35] [EMAIL PROTECTED] Recently I tried the latest release(4.2.2), and It works well if you manually copy libphp4.so.0 into Apache's libexec directory: $ cp .libs/libphp4.so.0 SOMEWHERE/apache/libexec/libphp4.so It means that 'make install-sapi' fails because there is no libphp4.so[.0] when 'install-sapi' tries to copy. To fix this problem, LIBTOOL must copy .libs/libphp4.so[.0] files into libs/ directory. I have a patch to resolve this problem at the following link: http://tclab.kaist.ac.kr/~cmlee/pub/php-4.2.2-20020730.patch I've tested the patch in the following environment: - AIX 4.3.3 - GNU gcc 2.95.3 - Apache 1.3.26 - PHP 4.2.2 Hope this help to close this problem and the patch come to no harm to others. :) -- CheolMin Lee ------------------------------------------------------------------------ [2002-01-29 16:36:08] [EMAIL PROTECTED] Sorry about last comment, I was a bit stressed out earlier! My environment is: AIX 4.3.3.0 PHP 4.1.1 Apache 1.3.22 VAC.C 5.0.0.2 (IBM Visual Age C Compiler) I think there's a definite problem with your make install script though with regards to extracting the libphp4.so to /apache/libexec. I got round that with ar -x libphp4.a and then running make install again. Also there's something wrong when I dynamically load the library because it's causing a coredump. It's really frustrating. I remember having exactly the same problem on Solaris a few months ago, but I've forgotten what I did to fix it (even more frustrating!). I thought it was something to do with a linker PATH variable? Do I need to set some variable to point at /usr/local/include/php? Should I change something in the php.ini file? I really don't want to change compilers at this stage because everything else is working fine with VAC. Does this have anything to do with the compiler fix mentioned in BUG 4630? I'll try that tomorrow. OK Well that's all I can think of. My configure was pretty basic: ./configure --with-apxs=/opt/apache/bin/apxs --without-mysql Are there some other options I should have added? Cheers, JS. ------------------------------------------------------------------------ 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/11716 -- Edit this bug report at http://bugs.php.net/?id=11716&edit=1