On Thu, 4 Oct 2001, Rick Cross wrote:

> When I run ./configure (with or without the --with-ssl directive) I get the
> following (excerpted from the whole output:
>
> checking for CRYPTO_lock in -lcrypto... yes
> checking for CRYPTO_add_lock in -lcrypto... yes
> checking for SSL_connect in -lssl... yes
> checking for openssl/x509.h... no
> checking for openssl/rsa.h... no
> checking for openssl/crypto.h... no
> checking for openssl/pem.h... no
> checking for openssl/ssl.h... no
> checking for openssl/err.h... no
> checking for x509.h... no
> checking for rsa.h... no
> checking for crypto.h... no

This proves that your OpenSSL include headers are not found by the configure
script, and that's why it gets built with SSL disabled.

I really can't see why this happens. Can you copy some relevant pieces from
your config.log and show us (regarding finding these headers) ? Search for
x509 and you'll find the place where it logged how it checked for these
headers. It should be a series of 'gcc -E' invokes.

> CPPFLAGS="-I/usr/local/ssl/include/openssl" LDFLAGS="-L/usr/lib"
> ./configure
>
> but it just leaves me at a > prompt.

Then you must be doing something wrong. If you're running a (ba)sh shell,
with all that on one single line, it simply should work (it runs the script
with the specified environment variables set). If you're using a (t)csh
shell, you should prefix that same line with 'env'.

Uh, btw, use "CPPFLAGS="-I/usr/local/ssl/include" as the "openssl" part will
be tested by the script anyway. Not that this would be the cause for the
failure anyway...

-- 
    Daniel Stenberg -- curl groks URLs -- http://curl.haxx.se/