Re: aclocal.m4 and openssl

[Guy Harris <guy () alum mit edu>]

On Sat, Apr 03, 2004 at 05:44:55PM -0500, Michael Richardson wrote:
> It appears that we don't really do the right with:
>
>    ./configure --with-crypto=/path 
>    ./configure --with-openssl=/path
>    ./configure --with-ssleay=/path
>
> (I'm uncertain which of these is right)

"--with-openssl" and "--with-ssleay" aren't in the configure script, but
there's no checks done for --with options, so they don't return an
error, they just don't do anything.  ("--with-a-cherry-on-top" also
produces no error. :-))

> - --with-crypto=/path seems to actually kill crypto.

That's the one of those three options that *does* do something.

> I want it to work like we look for libpcap.  
> Ideally, I'd like to include ${prefix} first. I think that this is easy
> to do in configure.in.
>
> But, my question is - about aclocal.m4 and the pcap checking stuff.
> Was that hand written, or did something generate it?

AC_LBL_LIBPCAP was, as far as I know, hand-written.
-
This is the tcpdump-workers list.
Visit https://lists.sandelman.ca/ to unsubscribe.