head 1.8; access; symbols netbsd-11-0-RC6:1.8 netbsd-11-0-RC5:1.8 netbsd-11-0-RC4:1.8 netbsd-11-0-RC3:1.8 netbsd-11-0-RC2:1.8 netbsd-11-0-RC1:1.8 perseant-exfatfs-base-20250801:1.8 netbsd-11:1.8.0.2 netbsd-11-base:1.8 netbsd-10-1-RELEASE:1.1 perseant-exfatfs-base-20240630:1.7 perseant-exfatfs:1.7.0.2 perseant-exfatfs-base:1.7 netbsd-10-0-RELEASE:1.1 netbsd-10-0-RC6:1.1 netbsd-10-0-RC5:1.1 netbsd-10-0-RC4:1.1 netbsd-10-0-RC3:1.1 netbsd-10-0-RC2:1.1 netbsd-10-0-RC1:1.1 netbsd-10:1.1.0.6 netbsd-10-base:1.1 cjep_sun2x-base1:1.1 cjep_sun2x:1.1.0.4 cjep_sun2x-base:1.1 cjep_staticlib_x-base1:1.1 cjep_staticlib_x:1.1.0.2 cjep_staticlib_x-base:1.1; locks; strict; comment @# @; 1.8 date 2025.03.30.09.51.51; author rillig; state Exp; branches; next 1.7; commitid veGmSzVhPiW2G4PF; 1.7 date 2023.06.01.20.56.35; author rillig; state Exp; branches 1.7.2.1; next 1.6; commitid j3tIvMRlxolKQhrE; 1.6 date 2023.02.25.19.24.07; author rillig; state Exp; branches; next 1.5; commitid K0kZnYsYbxG5rWeE; 1.5 date 2023.02.25.11.59.12; author rillig; state Exp; branches; next 1.4; commitid lxBaxWCbWIC5YTeE; 1.4 date 2023.02.25.11.11.16; author rillig; state Exp; branches; next 1.3; commitid WgBo5XDHyr60ITeE; 1.3 date 2023.02.25.09.02.45; author rillig; state Exp; branches; next 1.2; commitid HZAadegUXDZVZSeE; 1.2 date 2023.02.25.06.54.08; author rillig; state Exp; branches; next 1.1; commitid kFZ9gbXTJHyvhSeE; 1.1 date 2020.12.01.20.37.30; author rillig; state Exp; branches; next ; commitid cm7MFdMSBWFu45yC; 1.7.2.1 date 2025.08.02.05.58.40; author perseant; state Exp; branches; next ; commitid 23j6GFaDws3O875G; desc @@ 1.8 log @make: use '"filename" line 123' for locations instead of 'filename:123' The format 'filename:123' is commonly used for identifying a location in a file. Text editors recognize it and allow quick navigation through it. The previous format was specific to make and would have required custom support in editors. The new format was already used in stack traces, except for the first line. Now all lines use the same format. @ text @make: varname-dot-makeflags.mk:11: MAKEFLAGS= make: varname-dot-makeflags.mk:13: .MAKEFLAGS=< -r -k> make: varname-dot-makeflags.mk:15: .MAKEOVERRIDES=<> make: varname-dot-makeflags.mk:21: MAKEFLAGS= make: varname-dot-makeflags.mk:23: .MAKEFLAGS=< -r -k -D VARNAME -r> make: varname-dot-makeflags.mk:25: .MAKEOVERRIDES=< VAR> runtime: MAKEFLAGS=< -r -k -D VARNAME -r VAR=value> runtime: .MAKEFLAGS=< -r -k -D VARNAME -r> runtime: .MAKEOVERRIDES=< VAR> exit status 0 @ 1.7 log @tests/make: force line-based diagnostics to be listed in the tests This way, contradictions between the intended output and the actual output are closer together and have a better chance of being spotted. @ text @d1 6 a6 6 make: "varname-dot-makeflags.mk" line 11: MAKEFLAGS= make: "varname-dot-makeflags.mk" line 13: .MAKEFLAGS=< -r -k> make: "varname-dot-makeflags.mk" line 15: .MAKEOVERRIDES=<> make: "varname-dot-makeflags.mk" line 21: MAKEFLAGS= make: "varname-dot-makeflags.mk" line 23: .MAKEFLAGS=< -r -k -D VARNAME -r> make: "varname-dot-makeflags.mk" line 25: .MAKEOVERRIDES=< VAR> @ 1.7.2.1 log @Sync with HEAD @ text @d1 6 a6 6 make: varname-dot-makeflags.mk:11: MAKEFLAGS= make: varname-dot-makeflags.mk:13: .MAKEFLAGS=< -r -k> make: varname-dot-makeflags.mk:15: .MAKEOVERRIDES=<> make: varname-dot-makeflags.mk:21: MAKEFLAGS= make: varname-dot-makeflags.mk:23: .MAKEFLAGS=< -r -k -D VARNAME -r> make: varname-dot-makeflags.mk:25: .MAKEOVERRIDES=< VAR> @ 1.6 log @tests/make: clean up tests for MAKEFLAGS and related variables @ text @d1 6 a6 6 make: "varname-dot-makeflags.mk" line 10: MAKEFLAGS= make: "varname-dot-makeflags.mk" line 11: .MAKEFLAGS=< -r -k> make: "varname-dot-makeflags.mk" line 12: .MAKEOVERRIDES=<> make: "varname-dot-makeflags.mk" line 18: MAKEFLAGS= make: "varname-dot-makeflags.mk" line 20: .MAKEFLAGS=< -r -k -D VARNAME -r> make: "varname-dot-makeflags.mk" line 22: .MAKEOVERRIDES=< VAR> @ 1.5 log @tests/make: move tests for MAKRFLAGS to the correct file I had accidentally added these tests to the file for the special variable '.MAKEFLAGS' instead of the file for the environment variable 'MAKEFLAGS'. While here, add a basic test that shows how 'MAKEFLAGS' is built from '.MAKEFLAGS' and '.MAKEOVERRIDES'. @ text @d4 3 a6 3 make: "varname-dot-makeflags.mk" line 17: MAKEFLAGS= make: "varname-dot-makeflags.mk" line 18: .MAKEFLAGS=< -r -k -D VARNAME -r> make: "varname-dot-makeflags.mk" line 19: .MAKEOVERRIDES=< VAR> @ 1.4 log @tests/make: test that MAKEFLAGS is an environment variable @ text @d1 9 a9 20 spaces_stage_0: MAKEFLAGS=< -r -k > spaces_stage_0: env MAKEFLAGS=< -r -k > spaces_stage_1: MAKEFLAGS=< -r -k -d 00000 -D VARNAME WITH SPACES > spaces_stage_1: env MAKEFLAGS=< -r -k -d 00000 -D VARNAME WITH SPACES > dollars_stage_0: MAKEFLAGS=< -r -k > dollars_stage_1: env MAKEFLAGS=< -r -k DOLLARS=\$\{varname\}> dollars_stage_1: MAKEFLAGS=< -r -k DOLLARS=\{varname\}> dollars_stage_1: MAKEFLAGS:q=< -r -k DOLLARS=\{varname\}> dollars_stage_2: env MAKEFLAGS=< -r -k DOLLARS=> dollars_stage_2: dollars=<> dollars_stage_2: MAKEFLAGS=< -r -k DOLLARS=> dollars_stage_3: env MAKEFLAGS=< -r -k DOLLARS=> dollars_stage_3: dollars=<> dollars_stage_3: MAKEFLAGS=< -r -k DOLLARS=> append_stage_0: MAKEFLAGS=< -r -k > append_stage_1: MAKEFLAGS=< -r -k -D before-0 -D after-0 VAR0=value> append_stage_2: MAKEFLAGS=< -r -k -D before-0 -D after-0 -D before-1 -D after-1 VAR0=value VAR1=value> append_stage_3: MAKEFLAGS=< -r -k -D before-0 -D after-0 -D before-1 -D after-1 -D before-2 -D after-2 VAR0=value VAR1=value VAR2=value> override_stage_1: run MAKEFLAGS=< -r -k STAGE=1 VAR=value> override_stage_2: STAGE=<2> VAR= @ 1.3 log @tests/make: activate all tests for MAKEFLAGS @ text @d19 2 @ 1.2 log @tests/make: reproduce and explain '$' in MAKEFLAGS https://mail-index.netbsd.org/current-users/2023/02/24/msg043633.html @ text @d1 4 d15 4 @ 1.1 log @make(1): add test for the special .MAKEFLAGS variable @ text @d1 10 a10 2 echo "$MAKEFLAGS" -r -k -d 00000 -D VARNAME WITH SPACES @