On Thu, 2002-05-02 at 14:18, Stipe Tolj wrote: > I don't see the necessarity of chaning the configure.in behaviour. And > it *definitly* has changed. On a system without MySQL configure breaks > claiming that MySQL is not available. Hence we have a broken configure > here.
It's now fixed... mysql is disabled by default. The idea of --enable-* is to say we want and let configure discover where it is. The --with-*=path is to tell configure that the libs are there. But, yes, that's a bug... or mysql is disable by default and errors if user enables it and mysql is not found (user's fault), or if it remains enabled by default, it should just revert back to disabled if mysql is not found. > Bruno, could you please consider asking the developers list for votes > priour to commiting such changes. Thanks in advance. You know that, by Murphy's laws, nothing works at the first time ;)
