Re: Re: PHP 4.2.2 install woe: cannot stat libs/libphp.so
| From: | David Robley | Date: | Wed, 24 Jul 2002 23:49:17 +0000 |
| Subject: | Re: Re: PHP 4.2.2 install woe: cannot stat libs/libphp.so | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-109380@lists.php.net to get a copy of this message | ||
In article <1027515843.3284.11.camel@arcturus.phys.utk.edu>,
reubendb@innovativethought.com says...
> On Wed, 2002-07-24 at 08:29, Ian Ball wrote:
> > Assuming you are installing from your php-4.2.2 directory, it would appear
> > the libphp4.so hasn't actually been made, which would point to a possible
> > error in the configuration parameters. I am also assuming your php 4.2.1
> > made OK which would mean all necessary libraries etc are available on your
> > system. What are you using for the configure? On my system it was
> > ./configure --with-mysql --with-apxs=/usr/local/apache/bin/apxs
> > I did have ldap in there too, but for most people this is not necessary.
>
> Here is my configure line. Yes, my prev php 4.2.1 made and install fine
> with the same configure line. I did exactly the same steps as when I
> install 4.2.1
>
> /configure --with-mysql --enable-track-var --disable-debug
> --prefix=/usr/local/apache/php
> --with-config-file-path=/usr/local/apache/lib
> --with-apxs=/usr/local/apache/bin/apxs --with-gd --with-zlib
>
> >
> > If a fresh run from the start fails, then without further information, my
> > best suggestion is to completely delete the php-4.2.2 directory and ocntents,
> > and start again with the tar -zxf php-4.2.2.whatever, ./configure......
>
> I did that already, deleting the php-4.2.2 and start with un-tar the
> download. Many times. But still no luck.
>
> Thanks.
> Rdb
OK - after you do 'make' is there a file libphp4.so in the lib directory
under where you unpacked the install tarball? If not, something has
apparently gone wrong with the make process or the configure; you might
check (I think it is) config.log in the top of the install directory for
any clues.
I'm not sure, but it might be --enable-track-vars (unless that is a typo);
check with configure --help | grep track
Cheers
--
David Robley
Temporary Kiwi!
Quod subigo farinam