Date: Thu, 2 Oct 2003 12:13:59 -0700 (PDT) From: Doug Barton <DougB@FreeBSD.org> To: Dirk Meyer <dirk.meyer@dinoex.sub.org> Cc: freebsd-ports@freebsd.org Subject: Re: Need some USE_OPENSSL help Message-ID: <20031002120436.A677@znfgre.qbhto.arg> In-Reply-To: <1sAfJLJ75W@dmeyer.dinoex.sub.org> References: <20031002112026.O677@znfgre.qbhto.arg> <1sAfJLJ75W@dmeyer.dinoex.sub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2 Oct 2003, Dirk Meyer wrote:
> Doug Barton schrieb:,
>
> > 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.
>
> USE_OPENSSL=yes
> .include <bsd.port.pre.mk>
>
> will do ... if openssl is not in pase, the port will be included.
Actually I only needed .pre.mk to get OSVERSION, but thanks for the
info. BTW, including USE_OPENSSL does weird things with, for example,
make clean, since it always cleans perl and the openssl port. Also,
OPENSSLBASE is /usr/local, even though I have openssl in the base
system. Both of those behaviors seem broken to me, although I was able
to work around the first by just using --with-openssl.
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031002120436.A677>