php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #31780 Bug same as bug-id=14245
Submitted: 2005-01-31 16:20 UTC Modified: 2005-02-04 11:34 UTC
Votes:3
Avg. Score:5.0 ± 0.0
Reproduced:2 of 2 (100.0%)
Same Version:0 (0.0%)
Same OS:2 (100.0%)
From: bart8472 at gmail dot com Assigned:
Status: Not a bug Package: Compile Failure
PHP Version: 2.3.x OS: Debian Sarge
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: bart8472 at gmail dot com
New email:
PHP Version: OS:

 

 [2005-01-31 16:20 UTC] bart8472 at gmail dot com
Description:
------------
I have the same error as here: http://bugs.php.net/bug.php?id=14245 
And there is no libphp4.so is created. Same error on make install... everything is the same... and I even reinstalled whole debian and still I have the same error... Tried already on 4.3 stable and latest snapshot... This damn thing just doesn't compile as apache2 module!! 
What's UP :| I already spent 20 hours NON-STOP trying to resolve this problem. 

Best Regards... Bazyli

btw. I'm on apache2.
This doesn't even compile correctly if I configure just with:
./configure --with-apxs2


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-01-31 17:27 UTC] rasmus@php.net
What is in your .libs directory after you compile?
You may have to do a libtoolize --force
 [2005-01-31 18:21 UTC] bart8472 at gmail dot com
My .libs have 2 files and one symlink, libphp4.a, libphp4.au (symlink) and libphp4.aui...

What will libtoolize --force do?

PS
I compiled php4.2.3 right now without any problems, so I assume that the problem only affects the 4.3.x
 [2005-02-04 11:34 UTC] bart8472 at gmail dot com
OK, I resolved the problem by adding these parameters to configure: --disable-cgi --enable-force-cgi-redirect 
Don't know why it worked that way, but it worked, and that's good news ;)
I hope you will fix that soon :)
 
PHP Copyright © 2001-2020 The PHP Group
All rights reserved.
Last updated: Mon Apr 06 11:01:25 2020 UTC