jonathan vanasco wrote:
[...]
Because I upgraded my MySQL server to 4.1.7, I tried to compile my
mod_php
with mysql + mysqli support. After some problems with double
"-lmysqlclient"
in Makefile (found solution in bugs.php.net), the new mod_php
compiled. But
after testing it with Apache, The webserver had segfaults and mod_perl
error
messages:
I think there is a conflict between the mysql extensions of PHP and Perl.
[...]
Yep. You're right. I've run into this a few times.
If I remember right, its a problem stemming from library collisions --
and there should be a bunch of info on google somwhere.
I don't remember what i did to get things to work, but a quick google
search just suggested that it might work if you compile php without
mysql built in -- I dont believe php needs the mysql stuff compiled in
to use it, its just a speed issue.
Right. It's documented here:
http://perl.apache.org/docs/1.0/guide/troubleshooting.html#_exit_signal_Segmentation_fault__11___with_mysql
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
