From owner-freebsd-ports Fri Aug 28 03:24:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA28401 for freebsd-ports-outgoing; Fri, 28 Aug 1998 03:24:04 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from axl.training.iafrica.com (axl.training.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA28358 for ; Fri, 28 Aug 1998 03:23:56 -0700 (PDT) (envelope-from sheldonh@axl.training.iafrica.com) Received: from sheldonh (helo=axl.training.iafrica.com) by axl.training.iafrica.com with local-esmtp (Exim 1.92 #1) id 0zCLfy-00049D-00; Fri, 28 Aug 1998 12:22:38 +0200 From: Sheldon Hearn To: ac199@hwcn.org cc: freebsd-ports@FreeBSD.ORG Subject: Re: lynx w/ SSLeay working: crypto.h diff In-reply-to: Your message of "Fri, 28 Aug 1998 03:31:56 -0400." Date: Fri, 28 Aug 1998 12:22:38 +0200 Message-ID: <15946.904299758@axl.training.iafrica.com> Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 28 Aug 1998 03:31:56 -0400, Tim Vanderhoek wrote: > Do you want to see SSLeay support merged into the FreeBSD port? I don't know enough about crypto restrictions to know how much effort is involved in making that happen, and I'm certainly not going to say I want it until I'm willing to do it myself. :-P > Are future versions of lynx expected to ship with SSL default? No. Acting on advice from Mark Murray, I snuffled around the FreeBSD base source and discovered that SSLeay's ''free_func'' identifier conflicts with a typedef in FreeBSD's zlib.h, which lynx #includes. I've reported the conflict to the SSLeay developers. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message