From owner-freebsd-ports Fri Aug 28 15:32:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02811 for freebsd-ports-outgoing; Fri, 28 Aug 1998 15:32:25 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from pozo.pozo.com (pozo.pozo.com [207.201.8.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02806 for ; Fri, 28 Aug 1998 15:32:08 -0700 (PDT) (envelope-from mantar@netcom.com) Received: from dual (DUAL [192.168.0.2]) by pozo.pozo.com (8.9.1/8.9.1) with SMTP id PAA23121; Fri, 28 Aug 1998 15:28:34 -0700 (PDT) (envelope-from mantar@netcom.com) Message-Id: <4.1.0.49.19980828152404.00a23370@192.168.0.1> X-Sender: null@192.168.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1.0.49 (Beta) Date: Fri, 28 Aug 1998 15:28:33 -0700 To: ac199@hwcn.org, Sheldon Hearn From: Manfred Antar Subject: Re: lynx w/ SSLeay working: crypto.h diff Cc: Tim Vanderhoek , freebsd-ports@FreeBSD.ORG In-Reply-To: References: <28544.904288775@axl.training.iafrica.com> Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- At 03:31 AM 8/28/98 -0400, Tim Vanderhoek wrote: >On Fri, 28 Aug 1998, Sheldon Hearn wrote: > >> On Thu, 27 Aug 1998 15:58:15 -0400, Tim Vanderhoek wrote: >> >> > I'd guess the error is in some interaction between the Lynx SSL >> > patches and SSLeay. Maybe a strange #define. >> >> And your advice? Should I just not worry about it as long as it works >> for me? > >I don't have any advice... > >I can tell you what I would do... (!= advice) > >I would experiment a little further and try to figure-out why >what you did works. Changing (*free_func) to (*f) in a function >prototype should not have any effect, _normally_. I would play >around and see if things like (*freefunc) work or not. >Particularly important, I'd look for any funny #defines, or any >other occurrences of "free_func" in any system headers, lynx >sources files, or SSLeay source files. > >What you do may be totally different. :-) > >Do you want to see SSLeay support merged into the FreeBSD port? >Are future versions of lynx expected to ship with SSL default? >When? You could just report it to the maintainer of the Lynx SSL >patches so that if they get any questions from other people >"Help! Your patches don't work for me", then they have some >suggestions. I got it to compile by removing --with-zlib from the ports Makefile and adding this to makefile.in SSL_LIBS= -L/usr/local/lib -lssl -lcrypto -lRSAglue -lrsaref works fine Manfred ============================== || mantar@netcom.com || || pozo@infinex.com || || Ph. (415) 681-6235 || ============================== -----BEGIN PGP SIGNATURE----- Version: PGP for Personal Privacy 5.5.3ia iQCVAwUBNecvEc1kBT1ALyktAQF/MQQAl6MhJq7gzvjoJi3gMtZTbXyt6A0SAA+D 0IWCi3SAH3iABXuww9skXD5RFmNbZFlJypX/hwOGLDSGr7PyUnzRLsgXb+GZRD/q v1S8qim4UzVjImq9+3dchEByhtrkB4QlDlm0QtsRmuyJRNURsJDKFZj5WnJaumTa nohL9F2jyaA= =PIaG -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message