>>
>> But this won't work as the configure bails out if no mysql headers/libs
>> are found..(when you use plain --with-mysql default paths are searched)
>
>The 'old' behavior, was to enable mysql by default, because of the bundled libs
>and then issue a warning about using them.
>
>The 'new' behavior disables mysql by default and bails out on any config
>errors, which means you are left with the enabled by default stuff.
Do I need to say that that sentence doesn't make any sense? :)
OK: PHP 4.3: ./configure -> builds mysql with bundled libs PHP 5: ./configure -> does NOT build mysql
Best regards,
Melvyn Sopacua
----------------------------------------------------- \ Email Quoting, the forgotten art: / / http://www.kassj.com/netiquette/netiquette.html#5 \ -----------------------------------------------------
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
