[pkgsrc/trunk]: pkgsrc/regress/infra-unittests regress/infra-unittests: docum...

[rillig <rillig%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/95761e4c6e3b
branches:  trunk
changeset: 432530:95761e4c6e3b
user:      rillig <rillig%pkgsrc.org@localhost>
date:      Sat May 23 07:30:18 2020 +0000

description:
regress/infra-unittests: document creative AC_ARG_WITH in lang/mono4

diffstat:

 regress/infra-unittests/gnu-configure-strict.sh |  15 ++++++++++++++-
 1 files changed, 14 insertions(+), 1 deletions(-)

diffs (30 lines):

diff -r a305417d6368 -r 95761e4c6e3b regress/infra-unittests/gnu-configure-strict.sh
--- a/regress/infra-unittests/gnu-configure-strict.sh   Sat May 23 07:28:54 2020 +0000
+++ b/regress/infra-unittests/gnu-configure-strict.sh   Sat May 23 07:30:18 2020 +0000
@@ -1,5 +1,5 @@
 #! /bin/sh
-# $NetBSD: gnu-configure-strict.sh,v 1.3 2020/05/22 15:21:15 rillig Exp $
+# $NetBSD: gnu-configure-strict.sh,v 1.4 2020/05/23 07:30:18 rillig Exp $
 #
 # Tests for GNU_CONFIGURE_STRICT handling in mk/configure/gnu-configure.mk.
 #
@@ -412,6 +412,19 @@
        # or disable, but not both.  Therefore the simplest solution is to
        # scan for the common pattern ${enable_http+set}.
 
+       # In lang/mono4, the option name "libgc" creatively differs from
+       # the name "gc" that is mentioned in the help text:
+       #
+       # AC_ARG_WITH(libgc,
+       #   [  --with-gc=...],
+       #   [libgc=$with_gc],
+       #   [libgc=$libgc_default]
+       # )
+       #
+       # This way, even though --with-gc is documented in the help,
+       # specifying it triggers the "unrecognized options: --with-gc"
+       # warning 3 times, once for each configure script.
+
        create_file 'configure' <<-EOF
                if test "\${enable_http+set}" = set; then
                        :