From owner-freebsd-current Mon Jan 17 14:40:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from m0.cs.berkeley.edu (m0.CS.Berkeley.EDU [128.32.45.176]) by hub.freebsd.org (Postfix) with ESMTP id 718DB14E52; Mon, 17 Jan 2000 14:40:14 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca7-245.ix.netcom.com [209.109.235.245]) by m0.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id OAA59795; Mon, 17 Jan 2000 14:39:48 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id OAA03096; Mon, 17 Jan 2000 14:38:57 -0800 (PST) To: Kris Kennaway Cc: ports@freebsd.org, current@freebsd.org Subject: Re: cvs commit: src/secure/lib/libcrypto Makefile.inc Makefile References: From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) Date: 17 Jan 2000 14:38:53 -0800 In-Reply-To: Kris Kennaway's message of "Mon, 17 Jan 2000 11:33:43 -0800 (PST)" Message-ID: Lines: 15 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Kris Kennaway * 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). Well, the whole point is to standardize it, ala Motif and perl. Maybe we can pass OPENSSLINCLUDES and OPENSSLLIBS in CONFIGURE_ENV? Can you come up with a list of pathnames that are used in openssl-requiring ports? Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message