ID: 28590 User updated by: u60149431 at bedug dot com Reported By: u60149431 at bedug dot com -Status: No Feedback +Status: Open Bug Type: *Compile Issues Operating System: Fedora Core 2 PHP Version: 4.3.6 New Comment:
I linked it against a MySQL built from sources. I was able to make a workaround for this bug by editing the MySQL header file where a default was defined. What meaning does --with-mysql-sock have if it doesn't have any effect??? Previous Comments: ------------------------------------------------------------------------ [2004-06-10 01:00:03] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2004-06-01 22:39:28] [EMAIL PROTECTED] Are you compiling the MySQL extension against external or bundled libmysql? Check your phpinfo() output, what does MYSQL_SOCKET show for it's value? ------------------------------------------------------------------------ [2004-05-31 10:04:33] u60149431 at bedug dot com Description: ------------ The option --with-mysql-sock to the configure script is completely ignored, and causes PHP to still access /tmp/mysql.sock, which is the hard-coded value from header files. Any alternate values from /etc/my.cnf are also ignored. Use of php.ini is not feasible in my specific application. Expected result: ---------------- That --with-mysql-sock indicates the default value for the mysql socket. (which may be altered by a config file) ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=28590&edit=1
