[vox-tech] php4-cgi/mysql on debian woody: interesting note

[dylan]

Hi--

noticed something a little odd about debian (woddy), and php4-cgi/mysql

Background: 

I am running identical versions of debian (stable) , mysql, and php4 on 2
different x86 boxes.

dpkg -l | grep php4 produces the same on both machines:
ii  php4           4.1.2-6woody3  A server-side, HTML-embedded s
ii  php4-apc       1.1.0pl1-6     Caches PHP scripts to get them
ii  php4-cgi       4.1.2-6woody3  A server-side, HTML-embedded
ii  php4-mysql     4.1.2-6woody3  MySQL module for php4
ii  php4-pear      4.1.2-6woody3  PEAR - PHP Extension and Applicat

dpkg -l | grep mysql produces the same on both machines:
ii  libdbd-mysql-p 1.2216-2       mySQL database interface for Perl
ii  libmysqlclient 3.23.49-8.5    mysql database client library
ii  mysql-client   3.23.49-8.5    mysql database client binaries
ii  mysql-common   3.23.49-8.5    mysql database common files
ii  mysql-server   3.23.49-8.5    mysql database server binaries
ii  php4-mysql     4.1.2-6woody3  MySQL module for php4


however: 
on one machine `php4 -m` (the cgi version of php4) shows that it has support
for mysql....

whereas, on the other machin `php4 -m` shows that there is no support for
mysql.....

the apache module for php works perfectly with mysql on BOTH machines

i tried moving a copy of 'php4' from the working machine, but `php4 -m`
still reports no support for mysql....


Solution:

after checking '/etc/php4/cgi/php.ini' on both machines i noticed that one
had 'extension=mysql.so' at the very end...while the other (the one that
didn't work) did not. apparently the order in which i installed these
packages made some sort of difference, and i ended up with one working, and
one non-working machine. needless to say both are working just fine now.

just thought that i would share that.


Dylan

-- 
"The world is a dangerous place to live; not because of the people who are
evil, but because of the people who don't do anything about it."
-Albert Einstein