Re: misc/53561: Build log contains gmake debug output

[Andreas Gustafsson <gson%gson.org@localhost>]

The following reply was made to PR misc/53561; it has been noted by GNATS.

From: Andreas Gustafsson <gson%gson.org@localhost>
To: Martin Husemann <martin%duskware.de@localhost>
Cc: gnats-bugs%netbsd.org@localhost, matthew green <mrg%eterna.com.au@localhost>
Subject: Re: misc/53561: Build log contains gmake debug output
Date: Wed, 13 Nov 2019 17:58:35 +0200

 Martin Husemann wrote:
 >  Have you ever been able to reproduce this on any other host or outside
 >  of bracket? I wonder if there is something host specific that triggers
 >  it (like a hidden config file or a bug in libc that causes gmake to
 >  misbehave or something). It seems I can not reproduce it localy.
 
 I looked at four different bracket installations, including one
 hosted on Linux, and it happen on all of them.  For example:
 
 lyta.netbsd.org /bracket $ grep -c 'Live child 0x' */test/*/build.log
 evbarm-aarch64/test/2019.11.08.14.30.17/build.log:464
 evbarm-aarch64/test/2019.11.10.06.47.30/build.log:395
 evbarm-aarch64/test/2019.11.11.04.04.29/build.log:536
 evbarm-aarch64/test/2019.11.12.05.13.29/build.log:471
 evbarm-aarch64/test/2019.11.13.02.54.59/build.log:359
 evbarm-earmv7hf/test/2019.11.06.23.17.37/build.log:531
 evbarm-earmv7hf/test/2019.11.08.00.35.16/build.log:419
 [etc]
 
 gumbo.gson.org /bracket $ grep -c 'Live child 0x' */test/*/build.log
 amd64/test/2018.03.16.08.48.34/build.log:452
 hpcmips/test/2019.06.26.12.30.13/build.log:450
 [etc]
 
 The build log from a build I did manually outside of bracket did not
 contain any 'Live child' messages, even though the logs from builds
 done under bracket on the same machine do, so it looks like the bug
 is somehow triggered by bracket.
 
 Note that the line identified by mrg,
 
    GMAKE_J_ARGS?=  ${MAKEFLAGS:[*]:M*-j*:C/.*(-j ?[0-9]*).*/\1/W}
 
 is already known to have a bug that is triggered by doing the build in
 a directory called "saint-john" but not one called "saint-mary" (I kid
 you not, see PR 54456), so I would not be surprised if it has other
 equally bizarre bugs triggered by equally incidental circumstances.
 -- 
 Andreas Gustafsson, gson%gson.org@localhost