Sync the logic that decides whether to pull in openssl with the makefile
logic that decides whether to use -lcrypto. These need to stay the same to avoid the possibility of getting a silent dependence on a (possibly very old) builtin openssl. Of course, all it uses -lcrypto for is MD5, but still... PKGREVISION -> 1. XXX: this probably shouldn't be using MD5 anyway :-/
This commit is contained in:
parent
b5690f5ec3
commit
f25e49319b
1 changed files with 9 additions and 2 deletions
|
@ -1,7 +1,8 @@
|
|||
# $NetBSD: Makefile,v 1.22 2015/07/12 05:31:47 dholland Exp $
|
||||
# $NetBSD: Makefile,v 1.23 2015/07/12 05:36:50 dholland Exp $
|
||||
#
|
||||
|
||||
DISTNAME= dtcpclient-20090812
|
||||
PKGREVISION= 1
|
||||
CATEGORIES= net
|
||||
MASTER_SITES= http://www.imasy.or.jp/~ume/ipv6/ \
|
||||
http://home.jp.FreeBSD.org/~ume/ipv6/
|
||||
|
@ -31,7 +32,13 @@ BUILD_DEFS+= VARBASE
|
|||
INSTALLATION_DIRS= ${PKGMANDIR}/cat8 ${PKGMANDIR}/man8 sbin
|
||||
|
||||
.include "../../mk/bsd.prefs.mk"
|
||||
.if ${OPSYS} == "Darwin"
|
||||
|
||||
# Keep this in sync with patch-aa, as that determines whether -lcrypto
|
||||
# is used and if we get it wrong we'll get a silent dependency on
|
||||
# builtin openssl on platforms where that exists, which isn't good.
|
||||
.if ${OPSYS} != "NetBSD" || ${OPSYS} != "OpenBSD" || \
|
||||
${OPSYS} != "FreeBSD" || ${OPSYS} != "DragonFly"
|
||||
.include "../../security/openssl/buildlink3.mk"
|
||||
.endif
|
||||
|
||||
.include "../../mk/bsd.pkg.mk"
|
||||
|
|
Loading…
Reference in a new issue