i must be missing something simple since i can't make any sense of
what seem to be just plain inconsistencies in the curl configure
process. here's another simple example, regarding selecting support
for SPNEGO:

  $ ./configure
  ...
  checking if Kerberos4 support is requested... no
  checking if SPNEGO support is requested... no (good)
  checking if GSSAPI support is requested... no
  ...
  krb4 support: no (--with-krb4*)
  GSSAPI support: no (--with-gssapi)
  SPNEGO support: no (--with-spnego) (again, good)
  ...

so, i don't select SPNEGO support, and everything about the configure
output seems to support that. so far, so good.

  so, what if i run:

  $ ./configure --without-spnego

which you'd think would be totally redundant, right?

  ...
  checking if Kerberos4 support is requested... no
  checking if SPNEGO support is requested... yes (huh????)
  checking if GSSAPI support is requested... no

  checking for CRYPTO_lock in -lcrypto... no
  checking for CRYPTO_add_lock in -lcrypto... no
  configure: WARNING: SSL disabled, you will not be able to use HTTPS,
        FTPS, NTLM and more.
  configure: WARNING: Use --with-ssl or --with-gnutls to address this.
  ...
  checking for curl_off_t... yes
  checking size of curl_off_t... configure: error: cannot compute sizeof (curl_off_t), 77
  See `config.log' for more details.

whaaaa? why did that happen? none of this makes any sense. can
someone clarify what's going on here?

rday
Received on 2005-07-19