Date: Fri, 17 May 1996 14:25:51 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: njensen@habaneros.com (Neil C. Jensen) Cc: questions@freebsd.org Subject: Re: difficulties compiling SSLeay on 2.1R Message-ID: <199605172125.OAA20764@phaeton.artisoft.com> In-Reply-To: <01BB4377.51A41E60@jalapeno.habaneros.com> from "Neil C. Jensen" at May 16, 96 10:30:41 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> I'm attempting to compile SSLeay (both 5.2a from Oz and 5.1b from the = > ports collection), however, I consistently run into the following error: > > making all in txt_db... > making ssl... > making rsaref... > making apps... > gcc -o ssleay -I../include -D_ANSI_SOURCE -DHAVE_MD -O2 -m486 -Wall = > ssleay.o ver > ify.o asn1parse.o req.o dgst.o dh.o enc.o gendh.o errstr.o ca.o crl.o = > rsa.o x50 > 9.o genrsa.o s_server.o s_client.o s_filter.o speed.o hashdir.o = > s_time.o s_mult > .o apps.o s_cb.o s_socket.o s_eio.o version.o -L. -L.. -L../.. = > -L../../.. ../lib > ssl.a ../libcrypto.a -ldes -lmd > ld: -ldes: no match > *** Error code 1 > > I have read the FAQ and the handbook and understand (or so I thought) = > the md5/DES situation. My system is using md5. Is this causing the = > problem?=20 > > Any thoughts or pointers greatfully accepted. The source may or may not handle non-DES crypt. I believe it won't, actually. You will need to link -ldescrupt *before* the other crypto lib to get the DES routines instead. SSL requires the use of real DES. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605172125.OAA20764>