On 2016-06-27, Stuart Henderson <s...@spacehopper.org> wrote:
> ...but there's also this in config.site, which seems incorrect:
>
> ac_cv_prog_AWK=${ac_cv_prog_AWK=awk}
If you mean that it should use the full path, then no, it's correct
as is. Putting /usr/bin/awk there causes build errors, because
some of the autoconf magic that uses ac_cv_prog_AWK can't handle a
full path.
We have:
config.site:
ac_cv_prog_AWK=${ac_cv_prog_AWK=awk}
config.no-gawk:
ac_cv_prog_AWK=${ac_cv_prog_AWK=/usr/bin/awk}
Since ac_cv_prog_AWK is already set, the entry in config.no-gawk
is never used. Instead we want to set ac_cv_path_AWK in config.no-gawk.
I suggest the patch below. I've had this in the last two amd64
bulk builds. Yes, here the full path is fine.
OK?
Index: config.no-gawk
===================================================================
RCS file: /cvs/ports/infrastructure/db/config.no-gawk,v
retrieving revision 1.1
diff -u -r1.1 config.no-gawk
--- config.no-gawk 12 Dec 2011 10:33:33 -0000 1.1
+++ config.no-gawk 6 Jul 2016 21:39:46 -0000
@@ -1,3 +1,3 @@
# $OpenBSD: config.no-gawk,v 1.1 2011/12/12 10:33:33 jasper Exp $
# included unless lang/gawk
-ac_cv_prog_AWK=${ac_cv_prog_AWK=/usr/bin/awk}
+ac_cv_path_AWK=${ac_cv_path_AWK=/usr/bin/awk}
--
Christian "naddy" Weisgerber na...@mips.inka.de
