From owner-freebsd-ports@FreeBSD.ORG  Thu Oct  2 11:22:14 2003
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1E01F16A4B3
	for <freebsd-ports@freebsd.org>; Thu,  2 Oct 2003 11:22:14 -0700 (PDT)
Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 970D243FE5
	for <freebsd-ports@freebsd.org>; Thu,  2 Oct 2003 11:22:13 -0700 (PDT)
	(envelope-from DougB@freebsd.org)
Received: from master.dougb.net (12-234-18-52.client.attbi.com[12.234.18.52])
          by comcast.net (rwcrmhc12) with SMTP
          id <2003100218221301400bkn3ve>; Thu, 2 Oct 2003 18:22:13 +0000
Date: Thu, 2 Oct 2003 11:22:12 -0700 (PDT)
From: Doug Barton <DougB@FreeBSD.org>
To: freebsd-ports@freebsd.org
Message-ID: <20031002112026.O677@znfgre.qbhto.arg>
Organization: http://www.FreeBSD.org/
X-message-flag: Outlook -- Not just for spreading viruses anymore!
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Need some USE_OPENSSL help
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Oct 2003 18:22:14 -0000

Folks,

The following worked just fine for a long time:

.include <bsd.port.pre.mk>

.if ${OSVERSION} >= 400014
USE_OPENSSL=    yes
CONFIGURE_ARGS+=        --with-openssl=${OPENSSLBASE}
.endif


However, something broke recently, and now this no longer works. So, I
need to know how to get equivalent functionality with however things are
supposed to work today.

Thanks,

Doug

-- 

    This .signature sanitized for your protection