Re: [PHP4BETA] PHP4+apache+mysql problem
| From: | Sascha Schumann | Date: | Mon, 13 Dec 1999 23:38:53 +0000 |
| Subject: | Re: [PHP4BETA] PHP4+apache+mysql problem | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-7879@lists.php.net to get a copy of this message | ||
On Mon, Dec 13, 1999 at 05:34:17PM -0500, miguel222@mindless.com wrote:
> I sent the following email to both Apache and Zend, and was
> told by Andi Gutmans of Zend to report this problem here.
>
> At 02:00 PM 12/12/99 -0600, Michael Duff wrote:
> >I have recently downloaded php4 and apache 1.3.9, compiled them both
> >(which happens w/o error), but when I try to run the apache server
> >(httpd), I get the following error message:
> >
> >Syntax error on line 224 of /usr/local/apache/conf/httpd.conf:
> >Cannot load /usr/local/apache/libexec/libphp4.so into server:
> >/usr/local/apache/libexec/libphp4.so: undefined symbol: open64
> >
> >I built apache with:
> > --prefix=/usr/local/apache
> > --enable-shared=max
> >
> >then I built php4 with:
> > --with-mysql=/usr/src/mysql
> > --with-apxs=/usr/local/apache/bin/apxs
> > --with-config-file-path=/usr/local/apache
> >
> >My system is a Debian GNU/Linux 2.1 system, running under kernel 2.2.1
>
> Since that email, I have performed more exhaustive searching on
> several major engines, and found about six messages on DevShed
> from others saying basically "me too", and one on php's website
> in the user-submitted notes in their online documentation.
>
> I have also found that this problem (different error messages,
> but same function; open64) exists no matter how I compile php4,
> wether it be module, DSO, etc.
>
> In doing this, I noticed that it might bear some connection
> with mysql as well, (of which I am using version 3.23.7 alpha).
You use a binary MySQL distribution which was compiled
against a recent glibc 2.1 which contains support for LFS.
Your system uses an older version of glibc and thus does not
have any of the LFS functions.
Solution:
1.) Compile MySQL yourself
or
2.) Upgrade to a recent glibc 2.1.x
> Is the answer to this problem known? I've read one vague (and
> sketchy) reference to glibc, but there weren't any details with
> which to reach a solution.
Btw, please press enter after 75 chars per line or enable the
line wrap function in your email client. Thanks.
--
Regards,
Sascha Schumann
Consultant