php-install Digest 9 Aug 2002 18:11:15 -0000 Issue 971

Topics (messages 8058 through 8062):

failed build with apache 2.0.39 and default install of php 4.2.2
        8058 by: Ryan C. Creasey
        8060 by: Bob Lockie
        8061 by: Ryan C. Creasey

symbol __eprintf: referenced symbol not found
        8059 by: Lapt Chan

compile PHP --with-imap, on OS X: progress, but...
        8062 by: Michael Geary

Administrivia:

To subscribe to the digest, e-mail:
        [EMAIL PROTECTED]

To unsubscribe from the digest, e-mail:
        [EMAIL PROTECTED]

To post to the list, e-mail:
        [EMAIL PROTECTED]


----------------------------------------------------------------------
--- Begin Message ---
I'm running fbsd 4.6, with a new port tree.  I've installed apache-2.0.39
via ports and it runs just fine.  However, after trying to install the
mod_php4 port, using only the mysql and zlib options (well, and the
WITH_APACHE2 var defined as well), it runs into an error here:

Configuring SAPI modules
checking for AOLserver support... no
checking for Apache 1.x module support via DSO through APXS... no
checking for Apache 1.x module support... no
checking for mod_charset compatibility option... no
checking for Apache 2.0 module support via DSO through APXS... configure:
error: ZTS currently requires working POSIX threads. We were unable to
verify that your system supports Pthreads.

And as the config.log suggests:
configure:3548: checking for AOLserver support
configure:3624: checking for Apache 1.x module support via DSO through APXS
configure:3756: checking for Apache 1.x module support
configure:3943: checking for mod_charset compatibility option
configure:4013: checking for Apache 2.0 module support via DSO through APXS

I'm a long time user of the fbsd ports and php alike.  I've reinstalled
ports and apache several times, all yielding the same results.  Any
suggestions?

Ryan C. Creasey
Network Engineer
p11creative

--- End Message ---
--- Begin Message ---
On Thu, 8 Aug 2002 15:51:05 -0700, Ryan C. Creasey wrote:

>I'm running fbsd 4.6, with a new port tree.  I've installed apache-2.0.39
>via ports and it runs just fine.  However, after trying to install the
>mod_php4 port, using only the mysql and zlib options (well, and the
>WITH_APACHE2 var defined as well), it runs into an error here:
>
>Configuring SAPI modules
>checking for AOLserver support... no
>checking for Apache 1.x module support via DSO through APXS... no
>checking for Apache 1.x module support... no
>checking for mod_charset compatibility option... no
>checking for Apache 2.0 module support via DSO through APXS... configure:
>error: ZTS currently requires working POSIX threads. We were unable to
>verify that your system supports Pthreads.
>
>And as the config.log suggests:
>configure:3548: checking for AOLserver support
>configure:3624: checking for Apache 1.x module support via DSO through APXS
>configure:3756: checking for Apache 1.x module support
>configure:3943: checking for mod_charset compatibility option
>configure:4013: checking for Apache 2.0 module support via DSO through APXS
>
>I'm a long time user of the fbsd ports and php alike.  I've reinstalled
>ports and apache several times, all yielding the same results.  Any
>suggestions?

What is your configure command for PHP?
Run 'make clean' and 'rm config.cache' before you recompile.
Make sure you use --with-apxs2 for Apache2.



--- End Message ---
--- Begin Message ---
Well, each time I fail and rebuild I'm cleaning up the previous install... 
don't worry about that.  As for the configure commands, it's simply using 
the default --with-mysql --with-zlib, and the WITH_APACHE2 flag to the port,
 it adds --with-apxs2.

This is a combination of a FreeBSD ports problem and a configuration problem...
  I've already mailed the port maintainer, but I thought I'd try my hand
 here... I really don't know why this is happening the way it is; I was able
 to install apache-2.0.36 and php-4.2.1 just fine, under the same environment
 (In fact, this had taught me to do 'make builds' and preserving the installed
 version before I install the upgrade).

Any ideas for those who are familiar with this method?

- Ryan C. Creasey
  Network Engineer
  p11creative

Bob Lockie wrote:
> On Thu, 8 Aug 2002 15:51:05 -0700, Ryan C. Creasey wrote:
>=20
> >I'm running fbsd 4.6, with a new port tree.  I've installed apache-2.0.39
> >via ports and it runs just fine.  However, after trying to install the
> >mod_php4 port, using only the mysql and zlib options (well, and the
> >WITH_APACHE2 var defined as well), it runs into an error here:
> >
> >Configuring SAPI modules
> >checking for AOLserver support... no
> >checking for Apache 1.x module support via DSO through APXS... no
> >checking for Apache 1.x module support... no
> >checking for mod_charset compatibility option... no
> >checking for Apache 2.0 module support via DSO through APXS... configure:
> >error: ZTS currently requires working POSIX threads. We were unable to
> >verify that your system supports Pthreads.
> >
> >And as the config.log suggests:
> >configure:3548: checking for AOLserver support
> >configure:3624: checking for Apache 1.x module support via DSO through A=
PXS
> >configure:3756: checking for Apache 1.x module support
> >configure:3943: checking for mod_charset compatibility option
> >configure:4013: checking for Apache 2.0 module support via DSO through A=
PXS
> >
> >I'm a long time user of the fbsd ports and php alike.  I've reinstalled
> >ports and apache several times, all yielding the same results.  Any
> >suggestions?
>=20
> What is your configure command for PHP?=0B
> Run 'make clean' and 'rm config.cache' before you recompile.
> Make sure you use --with-apxs2 for Apache2.
>=20
>=20
>=20

----- End forwarded message -----
--- End Message ---
--- Begin Message ---
Need help

Tried updating php 2.1.1 to php 2.2.2

configure /make/make install stage went fine

but when i tried to start apache i get the following below:

(i've reinstalled php 2.1.1 without any problems)

OS = Solaris 8 with latest cluster patch

apache = v 1.3.22

cc = gcc version 2.95.3

dhcppc2 # /etc/init.d/apache start
httpd starting.
Syntax error on line 201 of /app/apache/conf/httpd.conf:
Cannot load /app/apache/libexec/libphp4.so into server: ld.so.1:
/app/apache/bin/httpd: fatal: relocation error: file
/app/apache/libexec/libphp4.so: symbol __eprintf: referenced symbol not
found
/app/apache/bin/apachectl start: httpd could not be started

line 201 of httpd.conf = LoadModule php4_module
/app/apache/libexec/libphp4.so

thanks

lapt



--- End Message ---
--- Begin Message ---
Hi folks,

I am desperately trying to get PHP (4.2.2) --with-imap running on OS X, 
so I can run the IMP web-mail client. I already have IMAP installed, and 
have downloaded and compiled the U-W c-client. I have also followed the 
directions on the PHP.NET website under IMAP.

Here is my PHP configure line:

./configure --prefix=/mg --with-apxs=/mg/sbin/apxs \
--with-config-file-path=/mg/etc --with-gettext=/sw \
--with-xml --enable-ftp --with-imap=/usr/local/src/imap-2002.RC2 \
--with-imap-ssl

I can configure PHP just fine, that is, I don't get any errors. However, 
when I run "make", I get a message:

*** Warning: This library needs some functionality provided by 
-lc-client.
*** I have the capability to make that library automatically link in when
*** you link to this library.  But I can only do this if you have a
*** shared version of the library, which you do not appear to have.
*** The inter-library dependencies that have been dropped here will be
*** automatically added whenever a program is linked with this library
*** or is declared to -dlopen it.

I do still get a libphp4.dylib file, but when I rename this to 
libphp4.so and place it in the appropriate apache directory, i get the 
following error from apache:

Syntax error on line 239 of /mg/etc/httpd.conf:
Cannot load /mg/libexec/httpd/libphp4.so into server: (reason unknown)

on line 239 of httpd.conf I have:

LoadModule php4_module          libexec/httpd/libphp4.so

Can anyone make any sense of this? I would really appreciate some help.

regards,

michael geary

--- End Message ---

Reply via email to