#18608 [Opn->Bgs]: PHP configure fails to locate MySQL header
| From: | rasmus@php.net | Date: | Sat, 27 Jul 2002 15:47:20 +0000 |
| Subject: | #18608 [Opn->Bgs]: PHP configure fails to locate MySQL header | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-15419@lists.php.net to get a copy of this message | ||
ID: 18608
Updated by: rasmus@php.net
Reported By: dholeman1@cox.net
-Status: Open
+Status: Bogus
Bug Type: MySQL related
Operating System: Redhat Linux 7.3
PHP Version: 4.2.1
New Comment:
--with-mysql=/usr/bin ??
PHP will look in path/include and path/lib for what it needs. You
obviously do not have /usr/bin/include and /usr/bin/lib so that path
you are providing is bogus. Simply use --with-mysql=/usr (assuming of
course you have installed the MySQL libs and header files)
Previous Comments:
------------------------------------------------------------------------
[2002-07-27 11:27:11] dholeman1@cox.net
When running configure on the Redhat binary release of PHP 4.2.1 in
order to include MySQL support (--with-MySQL=/usr/bin) the configure
script fails to look in the specified folder for the MySQL header files
and the script dies. The configure script is dedicated to looking only
in usr/local and since downstream variables build on the path simply
coding in a reference to the correct MySQL path does not work. There is
a current php/mysql path patch but that addresses a different, SOCKS
related, issue and not this one.
The problem has been noted over the last two years with various earlier
releases of PHP and MySQL. There are two current mentions of the
problem at
http://marc.theaimsgroup.com/?l=php-install&m=101437931602769&w=2
and
http://marc.theaimsgroup.com/?l=php-install&m=102239953422754&w=2,
plus
more if you google about the web.
Configuring with the mysql directive but without the path uses the
built in libraries but results in a warning that if MySQL is to be run
as an Apache module the php muct be onfigured using the mysql path and
not the default libraries.
Note that removing the MySQL directive, deleting the configure.cache
file and rerunning configure results in configure running to completion
but with the same warning as above.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=18608&edit=1