On Mon, 18 Jul 2005, Dan Fandrich wrote:

> Take a look at the config.log file for clues. If you get really
> desperate, you could run configure under the shell using the -x flag
> to see exactly what's going on and why it's not finding your libs
> and/or directories.

what confuses me is that i can do a native configure of curl *with*
ssl, even though SSL is not installed under the default location
/usr/local/ssl.

according to the "configure" file, the option is

  --with-ssl=PATH

where PATH is, by default, /usr/local/ssl. however, i can do a
successful configure just by using "--with-ssl". but if ssl is not
installed under /usr/local/ssl, how can this succeed?

just for fun, i tried:

  $ .configure --with-ssl=/home

which should certainly fail. it still worked. so what's up with this
option? it doesn't seem to make any sense.

rday
Received on 2005-07-18