From owner-freebsd-ports Fri Aug 28 00:33:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10609 for freebsd-ports-outgoing; Fri, 28 Aug 1998 00:33:52 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from localhost.my.domain (ppp1586.on.bellglobal.com [206.172.249.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10604 for ; Fri, 28 Aug 1998 00:33:50 -0700 (PDT) (envelope-from hoek@FreeBSD.ORG) Received: from localhost (tim@localhost) by localhost.my.domain (8.8.8/8.8.8) with SMTP id DAA00367; Fri, 28 Aug 1998 03:31:59 -0400 (EDT) (envelope-from ac199@hwcn.org) X-Authentication-Warning: localhost.my.domain: tim owned process doing -bs Date: Fri, 28 Aug 1998 03:31:56 -0400 (EDT) From: Tim Vanderhoek X-Sender: tim@localhost Reply-To: ac199@hwcn.org To: Sheldon Hearn cc: Tim Vanderhoek , freebsd-ports@FreeBSD.ORG Subject: Re: lynx w/ SSLeay working: crypto.h diff In-Reply-To: <28544.904288775@axl.training.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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. -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message