Date: Thu, 2 Mar 2000 15:12:46 +0200 (SAT) From: John Hay <jhay@mikom.csir.co.za> To: freebsd-ports@freebsd.org Subject: Mk/bsd.port.mk a little broken Message-ID: <200003021312.PAA85288@zibbi.mikom.csir.co.za>
next in thread | raw e-mail | index | archive | help
The current bsd.port.mk file is a little broken if you try to use a port
that define USE_OPENSSL on a fairly new -current machine without libcrypto.
The makefile will then have echo commands outside a target. Here is a
patch that try to fix it the same way it is done in other places.
One question that I have is, is it the intention to require that you
have libcrypto on -current machines even if you only want to do a
"make readmes" in the ports? I have a -current machine without the
crypto stuff in the base system that build daily releases (with
crypto in them), but it is failing now in ports when trying to do
"make readmes".
John
--
John Hay -- John.Hay@mikom.csir.co.za
Index: Mk/bsd.port.mk
===================================================================
RCS file: /home/ncvs/ports/Mk/bsd.port.mk,v
retrieving revision 1.329
diff -u -r1.329 bsd.port.mk
--- Mk/bsd.port.mk 2000/02/24 07:03:31 1.329
+++ Mk/bsd.port.mk 2000/03/02 04:09:42
@@ -574,6 +574,7 @@
.if defined(USE_OPENSSL)
.if ${OSVERSION} >= 400014
.if !exists(/usr/lib/libcrypto.a)
+.BEGIN:
@${ECHO} "This port requires the OpenSSL library, which is part of"
@${ECHO} "the FreeBSD crypto distribution but not installed on your"
@${ECHO} "machine. Please see Chapter 6.5 in the handbook for"
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003021312.PAA85288>