From owner-freebsd-current Mon Jan 17 12:39:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.254.39]) by hub.freebsd.org (Postfix) with ESMTP id 32D5114BFF; Mon, 17 Jan 2000 12:39:42 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id PAA43537; Mon, 17 Jan 2000 15:39:34 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <38837E05.72203F31@acm.org> Date: Mon, 17 Jan 2000 15:39:33 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Satoshi - Ports Wraith - Asami , ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Add lynx-ssl to the list of ports which are broken on current. This was as of Jan. 16 at 14:00 EST cvsup of ports and source followed by a make world. Jim Bloom bloom@acm.org Kris Kennaway wrote: > > On 17 Jan 2000, Satoshi - Ports Wraith - Asami wrote: > > > Should I add some stuff to handle the differences in bsd.port.mk (like > > we did with perl5)? > > It may be useful - although there are a lot of inconsistencies in how the > openssl ports look for it. Dirk Froemberg was going to help with this - > I'm not sure exactly what the best way to do it is. For example, ports > like w3m-ssl pass the location of the openssl include directory, which > needs to be either /usr/include or ${LOCALBASE}/include. Perhaps the best > thing would be to bump OSVERSION (belatedly). > > Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message