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

[Martin Husemann <martin%duskware.de@localhost>]

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

From: Martin Husemann <martin%duskware.de@localhost>
To: Andreas Gustafsson <gson%gson.org@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:11:32 +0100

 On Wed, Nov 13, 2019 at 05:58:35PM +0200, Andreas Gustafsson wrote:
 > 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.
 
 Yeah, -j triggering the match, but how does the directory get into
 MAKEFLAGS, and what triggers it in the bracket case?
 
 Can you try modifying the next line to echo some debug data, like:
 
 GMAKE_J_ARGS?=  ${MAKEFLAGS:[*]:M*-j*:C/.*(-j ?[0-9]*).*/\1/W}
 BUILD_COMMAND=  echo "MAKEFLAGS: ${MAKEFLAGS}; echo "GMAKE_J_ARGS: ${GMAKE_J_ARGS}; /usr/bin/env -i ${BUILD_ENV} ${MAKE_ARGS} ${TOOL_GMAKE} ${GMAKE$
 
 and grep for that in a bracket log?
 
 Martin