Re: Fwd: Re: [PHP4BETA] SegFault with php4, mod_perl and mod_ssl

On Mon, 12 Jun 2000, Sascha Schumann wrote: > On Mon, 12 Jun 2000, Zeev Suraski wrote: > > > I'd be very interested to hear if anybody has any creative ideas as to how > > to solve this problem. This is definitely a FAQ, it seems like loads of > > people are experiencing crashes due to MySQL incompatibilities, between the > > local client linked with their PHP 3.0/mod_perl/mod_auth_mysql, and the > > bundled MySQL library in PHP 4.0. > > > > If there was some way to detect it... I can't think of any way, but > > perhaps someone here can? > > > > If there's nothing we can actively do about it, I guess we should add it to > > the FAQ, and it may actually be important enough to add a note about this > > at the final configure message. > > There is a technical solution which is completely backwards > compatible. If the user specified --with-mysql without an > argument, we currently always choose the embedded mysql > client library. We can extend this mechanism to search again > for MySQL in the standard locations. If it finds MySQL, we > use the installed client library, otherwise the embedded > client library gets used. That's a good idea, and it is indeed backwards compatible, but it doesn't cover 100% of the problem. Users who know PHP 4.0 has built-in MySQL support will often not bother to add --with-mysql at all... I think the solution should be a combination of what you suggested, and a warning message at the end in case the bundled MySQL library was (implicitly) selected. Zeev -- Zeev Suraski <zeev@zend.com> http://www.zend.com/