From bbb0f5b68c844e3466c16567ccecff51a767b75f Mon Sep 17 00:00:00 2001 From: rillig Date: Sat, 23 May 2020 07:30:18 +0000 Subject: regress/infra-unittests: document creative AC_ARG_WITH in lang/mono4 --- regress/infra-unittests/gnu-configure-strict.sh | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) (limited to 'regress/infra-unittests') diff --git a/regress/infra-unittests/gnu-configure-strict.sh b/regress/infra-unittests/gnu-configure-strict.sh index 85f5a6100cd..56933183766 100644 --- a/regress/infra-unittests/gnu-configure-strict.sh +++ b/regress/infra-unittests/gnu-configure-strict.sh @@ -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 @@ if test_case_begin 'configure script without enable_http variable'; then # 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 : -- cgit v1.2.3