From owner-freebsd-questions  Fri May 17 14:30:53 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA21513
          for questions-outgoing; Fri, 17 May 1996 14:30:53 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA21472
          for <questions@freebsd.org>; Fri, 17 May 1996 14:30:44 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA20764; Fri, 17 May 1996 14:25:51 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199605172125.OAA20764@phaeton.artisoft.com>
Subject: Re: difficulties compiling SSLeay on 2.1R
To: njensen@habaneros.com (Neil C. Jensen)
Date: Fri, 17 May 1996 14:25:51 -0700 (MST)
Cc: questions@freebsd.org
In-Reply-To: <01BB4377.51A41E60@jalapeno.habaneros.com> from "Neil C. Jensen" at May 16, 96 10:30:41 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 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.