here's a minimal example of strangeness in the config process that
anyone should be able to reproduce:

  $ ./configure

  ...
  checking if argv can be written to... yes
  checking if Kerberos4 support is requested... no <--- good
  checking if SPNEGO support is requested... no
  ...

  $ ./configure --without-krb4 [should be redundant?]

  ...
  checking if argv can be written to... yes
  checking if Kerberos4 support is requested... krb4 is not compatible
        with IPv6

huh? i just *said* i didn't want krb4, and yet there it is. so what
if i explicitly disable ipv6?

  $ ./configure --without-krb4 --disable-ipv6

  checking if argv can be written to... yes
  checking if Kerberos4 support is requested... yes (?????????)
  checking where to look for Kerberos4... libs in no/lib, headers in
        no/include

i don't see any way that this makes sense. i *explicitly* state i
don't want krb4, the configuration process seems to think i requested
it, and yet, at the end of the config process, we read:

  curl version: 7.14.0
  Host setup: i686-pc-linux-gnu
  Install prefix: /usr/local
  Compiler: gcc
  SSL support: enabled (OpenSSL)
  zlib support: enabled
  krb4 support: no (--with-krb4*) (what the hell?)
  GSSAPI support: no (--with-gssapi)
  SPNEGO support: no (--with-spnego)
  c-ares support: no (--enable-ares)
  ipv6 support: no (--enable-ipv6)

thoughts?

rday
Received on 2005-07-19