Re: [bug-gawk] gawk 4.2.1 test failure on macOS

[Charles Diza]

On Mon, Feb 26, 2018 at 8:18 AM, Andrew J. Schorr <address@hidden> wrote:

On Sun, Feb 25, 2018 at 06:02:08PM -0500, Charles Diza wrote:
> Bisection on the gawk git repo reveals that
> bae14502b6389b7d81bf0841a35b4c9d9824ca10 Is the first bad gawk commit.
>
> During bisection, some of the "bad" stages had slightly different test
> failures than the one I'm reporting.  I labeled those "bad" and went on
> with the bisection.

FYI, the nlstringtest check that's failing was added on Jan 15, 2018, and the
bae14502b6389b7d81bf0841a35b4c9d9824ca10 commit was on Jan 4, 2018.  Did you
bisect by testing with "make check", or did you test each binary produced
using the latest test/nlstringtest.awk and test/nlstringtest.ok? As Arnold
pointed out, this failure is almost certainly due to the absence of gettext...

I bisected and at each "stage", did the ./configure,make,make check dance.

I'm hoping that some of these tests can be changed so that they aren't run if gettext isn't found.  gawk 4.2.0 didn't require gettext in order to have a passing test suite.

-Charles