summaryrefslogtreecommitdiff
path: root/mk/configure
diff options
context:
space:
mode:
authorrillig <rillig@pkgsrc.org>2019-04-20 16:32:42 +0000
committerrillig <rillig@pkgsrc.org>2019-04-20 16:32:42 +0000
commit74e1272849cad861881c4c6aa5a83c988864fe4b (patch)
tree9178a43e1b6a9ad3c70ed7ec0fd52d146cc9e5d6 /mk/configure
parent146f28326d34ecfd39210106d666238a1e27d0b5 (diff)
downloadpkgsrc-74e1272849cad861881c4c6aa5a83c988864fe4b.tar.gz
mk: fix pkglint warnings about ambiguous variables
When a Makefile fragment contains $0, this means a Makefile variable, not a shell or AWK variable. The bug in ccc.mk survived unnoticed for almost 15 years. The bug in gnu-configure.mk for MirBSD got only half as old.
Diffstat (limited to 'mk/configure')
-rw-r--r--mk/configure/gnu-configure.mk4
1 files changed, 2 insertions, 2 deletions
diff --git a/mk/configure/gnu-configure.mk b/mk/configure/gnu-configure.mk
index 257fd280455..db863adfd49 100644
--- a/mk/configure/gnu-configure.mk
+++ b/mk/configure/gnu-configure.mk
@@ -1,4 +1,4 @@
-# $NetBSD: gnu-configure.mk,v 1.18 2019/04/03 19:10:26 rillig Exp $
+# $NetBSD: gnu-configure.mk,v 1.19 2019/04/20 16:32:42 rillig Exp $
#
# Package-settable variables:
#
@@ -170,7 +170,7 @@ _SCRIPT.configure-scripts-osdep= \
found = 0; \
} \
} \
- { print $0 }' $$file >$$file.override; \
+ { print $$0 }' $$file >$$file.override; \
${CHMOD} +x $$file.override; \
${TOUCH} -r $$file $$file.override; \
${MV} -f $$file.override $$file