Date: Sun, 4 Jun 1995 01:26:28 -0700 From: asami@CS.Berkeley.EDU (Satoshi Asami) To: joerg_wunsch@uriah.heep.sax.de Cc: freebsd-ports@FreeBSD.org Subject: elm and descrypt (Re: UNIX crypt() source - the problem solved (fwd)) Message-ID: <199506040826.BAA02028@silvia.HIP.Berkeley.EDU> In-Reply-To: <199506040622.IAA25865@uriah.heep.sax.de> (message from J Wunsch on Sun, 4 Jun 1995 08:22:09 %2B0200 (MET DST))
next in thread | previous in thread | raw e-mail | index | archive | help
According to Joerg:
* Hmm, this reminds me of another pitfall. I don't know about Pine/
* IMAPD, but Elm requires to be linked against -ldescrypt, in order to
* get its internal message {en,de}cryption correct.
*
* Satoshi, the configure script in our port should be aware of this, and
* it might warn the user about the disfunctional encryption if there's
* no such thing like -ldescrypt available. (I don't know who's the
* maintainer of the elm port.)
Something like this?
post-configure:
if ! ldconfig | grep -q descrypt; then
echo "Seems like you don't have the DES crypt library (libdescrypt)."
echo "The internal message {en,de}cryption may be incorrect."
fi
Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506040826.BAA02028>