It appears to be the case that ${COMPILEETOBJ}/compile_et, which is used in
the USETOOLS=no and !defined(USETOOLS) cases, is not guaranteed to exist. However, the current functionality overrides any potentially correct hand-set definition of COMPILE_ET, causing build breakage. Now the line setting COMPILE_ET only happens if COMPILE_ET is not already set, like so: .if !defined(COMPILE_ET) COMPILE_ET= ${COMPILEETOBJ}/compile_et .endif
This commit is contained in:
parent
c32ec6cb78
commit
058f064635
|
@ -1,4 +1,4 @@
|
|||
# $NetBSD: Makefile,v 1.13 2001/10/06 21:51:53 perry Exp $
|
||||
# $NetBSD: Makefile,v 1.14 2001/10/11 03:39:02 mason Exp $
|
||||
|
||||
.include <bsd.own.mk>
|
||||
|
||||
|
@ -12,8 +12,10 @@ LIB= asn1
|
|||
|
||||
.if !defined(USETOOLS) || (${USETOOLS} == "no")
|
||||
COMPILEETOBJ!= cd ${.CURDIR}/../libcom_err/compile_et && ${PRINTOBJDIR}
|
||||
.if !defined(COMPILE_ET)
|
||||
COMPILE_ET= ${COMPILEETOBJ}/compile_et
|
||||
.endif
|
||||
.endif
|
||||
|
||||
asn1_err.h asn1_err.c: asn1_err.et
|
||||
${COMPILE_ET} ${DIST}/heimdal/lib/asn1/asn1_err.et
|
||||
|
|
Loading…
Reference in New Issue