Re: PHP 4.0 Bug #5669 Updated: /usr/local/apache/libexec/libphp3.so: undefined symbol: open64

From: Date: Sat, 22 Jul 2000 06:06:38 +0000
Subject: Re: PHP 4.0 Bug #5669 Updated: /usr/local/apache/libexec/libphp3.so: undefined symbol: open64
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-25402@lists.php.net to get a copy of this message
Newer versions of glibc supports 64-bit file operations. So the i686 MySQL client shoud be just fine, just upgrade your glibc to the newest (2.1.3), recompile apache and you're ok. ----- Original Message ----- From: "Bug Database" <php-dev@lists.php.net> To: <php-dev@lists.php.net> Sent: Saturday, July 22, 2000 05:28 Subject: [PHP-DEV] PHP 4.0 Bug #5669 Updated: /usr/local/apache/libexec/libphp3.so: undefined symbol: open64 > ID: 5669 > User Update by: shawn.m@microcore.net > Old-Status: Open > Status: Closed > Bug Type: Installation problem > Description: /usr/local/apache/libexec/libphp3.so: undefined symbol: open64 > > WOO HOO!!! I found out the error... So I guess I'm going to close this ticket myself. Here's what it is... > > For some reason in MySQL they have a i686 client, DO NOT get this client, as Apache does not know what the open64() is. > > When you specify the --with-mysql=/path/to/mysql/source/mysql (or what ever your path to the base of the MySQL source code is) It uses the functions et al out of the MySQL source. Well, in the MySQL source it has open64() calls that apparently Apache does not know. > > What does this mean? Apache is not 64bit software and MySQL is along with PHP? That's my guess... > > -Shawn > > Full Bug description available at: http://bugs.php.net/?id=5669

« previous php.dev (#25402) next »