On Mon, 4 Sep 2023, Christos Zoulas wrote:
Ok how about: ~/git/netbsd_src/distrib/sets$ MAKEVERBOSE=0 ~/data/netbsd/build/sparc64/tooldir/bin/nbmake-sparc64 -B -f mkvars.mk and ~/git/netbsd_src/distrib/sets$~/data/netbsd/build/sparc64/tooldir/bin/nbmake-sparc64 -B MAKEVERBOSE=0 -f mkvars.mk
opc@instance-20230726-2011:~/git/netbsd_src/distrib/sets$ MAKEVERBOSE=0 ~/data/netbsd/build/sparc64/tooldir/bin/nbmake-sparc64 -B -f mkvars.mk makeverbose echo 4 + echo 4 4 opc@instance-20230726-2011:~/git/netbsd_src/distrib/sets$ ~/data/netbsd/build/sparc64/tooldir/bin/nbmake-sparc64 -B MAKEVERBOSE=0 -f mkvars.mk makeverbose 0 opc@instance-20230726-2011:~/git/netbsd_src/distrib/sets$ ~/data/netbsd/build/sparc64/tooldir/bin/nbmake-sparc64 -B -f mkvars.mk MAKEVERBOSE=0 makeverbose 0 opc@instance-20230726-2011:~/git/netbsd_src/distrib/sets$So mkvars.mk respects the assigment of MAKEVERBOSE properly in the last two scenaarios so this is in sync with the documentation in make(1)
mkvars.mk is only referenced by sets.subr and I noticed that sets.subr is sourced by quite a few of the shell-scripts in the distrib/sets directory. I will continue down this path trying to figure out what the actual issue is.