Date: Thu, 12 May 2022 09:37:54 -0400
From: "Andrew J. Schorr" <aschorr@telemetry-investments.com>
Cc: Eli Zaretskii <eliz@gnu.org>, bug-gawk@gnu.org
What's going on in the middle part of the patch: it seems to be removing
the modification to AWKLIBPATH to append
`$(GAWKPROG) 'BEGIN {print ENVIRON["AWKLIBPATH"]}'`
What's the issue there?
I described that in my report. Let me repeat:
AWK = LC_ALL=$${GAWKLOCALE:-C} LANG=$${GAWKLOCALE:-C} AWKLIBPATH=../.libs:`$(GAWKPROG)
'BEGIN {print ENVIRON["AWKLIBPATH"]}'` [...]
The MinGW Gawk needs AWKLIBPATH with semi-colons, not colons. The
MSYS Bash I use converts colons to semi-colons before it invokes Gawk,
but it gets confused because 'BEGIN {print ENVIRON["AWKLIBPATH"]}'
produces a Windows-style d:/foo/bar file name with a colon after the
drive letter, so that colon also gets converted to a semi-colon.
Solution: a Sed script:
AWK = LC_ALL=$${GAWKLOCALE:-C} LANG=$${GAWKLOCALE:-C} AWKLIBPATH=../.libs:`$(GAWKPROG) 'BEGIN
{print ENVIRON["AWKLIBPATH"]}' | sed "s,d:/,/d/,"`
My proposal above, if you don't like doing it on all platforms, could
be modified to do that only on Windows, by having configure select one
of two possible commands when it produces test/Makefile from
test/Makefile.in.