> True, but it gets set back to "no" if the libraries are subsequently not > found. Not a problem though if Amos has changed it to a better way of > doing it.
The current standard for --enable and --with flags is: "yes" means force-enable, fail the build if not possible. "no" means force-disable, "auto" means "try to enable, disable if some required part is not available". For --with flags, everything else is usually considered as a path to be used. Please everyone remember that, let's not get the autoconf-refactor effort be wasted :) -- /kinkie
