That's what the ssl option in configure is for (do ./configure -help to
check exactly what it is it is - I don't have the source handy). You need to
supply the directory under where libcrypto is found. Eg if it is
/usr/local/openssl/lib/libcrypto.a then the option is
-with-???=/usr/local/openssl
If you don't tell configure where to find libcrypto.a then the tests for
libsnmp fail but the tests for the headers have already set the "I found
{ucd|net}-snmp" flag.
Make sure you have a more recent source than 0.8.16 - the config setup was
wrong in that version, and didn't exist before then.
Regards,
Andrew Hood
A distributed system is one in which the failure of a computer you didn't
even know existed can render your own computer unusable. -- Leslie Lamport,
as quoted in CACM, June 1992
-----Original Message-----
From: Bill Fumerola [mailto:billf@xxxxxx]
Sent: Wednesday, 18 April 2001 13:11
To: ethereal-dev@xxxxxxxxxxxx
Subject: [Ethereal-dev] ethereal build process broken
Developers,
I don't have a lot of time to look into this, but it seems
when the ethereal configure scripts find the snmp headers,
snmp is enabled and the snmp dissector is compiled with
libsnmp calls..
unfortunately when the link stage comes, the binaries aren't
linked with -lsnmp. They also aren't linked with -lcrypto
if its available, which is needed in recent versions of
ucd^Wnet-snmp.
could whoever is responsible for the ethereal build process
fix this (I've hacked around my local copy and it works by just
adding -lsnmp -lcrypto in the obvious places) so the freebsd
port can support snmp dissection.
thanks.
--
Bill Fumerola - security yahoo / Yahoo! inc.
- fumerola@xxxxxxxxxxxxx / billf@xxxxxxxxxxx
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
<<application/ms-tnef>>
