head	1.7;
access;
symbols
	netbsd-11-0-RC4:1.7
	netbsd-11-0-RC3:1.7
	netbsd-11-0-RC2:1.7
	netbsd-11-0-RC1:1.7
	perseant-exfatfs-base-20250801:1.7
	netbsd-11:1.7.0.2
	netbsd-11-base:1.7
	netbsd-10-1-RELEASE:1.2
	perseant-exfatfs-base-20240630:1.3
	perseant-exfatfs:1.3.0.2
	perseant-exfatfs-base:1.3
	netbsd-10-0-RELEASE:1.2
	netbsd-10-0-RC6:1.2
	netbsd-10-0-RC5:1.2
	netbsd-10-0-RC4:1.2
	netbsd-10-0-RC3:1.2
	netbsd-10-0-RC2:1.2
	netbsd-10-0-RC1:1.2
	netbsd-10:1.2.0.2
	netbsd-10-base:1.2
	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.7
date	2025.06.28.22.39.28;	author rillig;	state Exp;
branches;
next	1.6;
commitid	CDDpACH2g2jV3I0G;

1.6
date	2025.03.30.09.51.50;	author rillig;	state Exp;
branches;
next	1.5;
commitid	veGmSzVhPiW2G4PF;

1.5
date	2024.07.04.20.18.40;	author rillig;	state Exp;
branches;
next	1.4;
commitid	75IS4XOhTa8VOygF;

1.4
date	2024.07.04.17.47.54;	author rillig;	state Exp;
branches;
next	1.3;
commitid	mjDGVMgldk7QYxgF;

1.3
date	2023.08.19.10.52.13;	author rillig;	state Exp;
branches
	1.3.2.1;
next	1.2;
commitid	BookaqSA0CGHYnBE;

1.2
date	2022.01.23.21.48.59;	author rillig;	state Exp;
branches;
next	1.1;
commitid	tSU3TbL9LKI12OpD;

1.1
date	2020.09.13.09.20.23;	author rillig;	state Exp;
branches;
next	;
commitid	529xd5IHykbGRRnC;

1.3.2.1
date	2025.08.02.05.58.33;	author perseant;	state Exp;
branches;
next	;
commitid	23j6GFaDws3O875G;


desc
@@


1.7
log
@make: consistently use double quotes in error messages

Previously, some error messages used single quotes, very few used
backticks or parentheses, most already used double quotes.

While here, reword a few error messages to be clearer or more consistent
with related error messages.
@
text
@make: directive-dinclude-error.inc:1: Invalid line "syntax error"
	in directive-dinclude.mk:21
make: Fatal errors encountered -- cannot continue
make: stopped making "all" in unit-tests
exit status 1
@


1.6
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
@d1 1
a1 1
make: directive-dinclude-error.inc:1: Invalid line 'syntax error'
@


1.5
log
@make: on error, print the targets to be made

This helps to understand situations with several nested sub-makes in
varying directories.
@
text
@d1 1
a1 1
make: "directive-dinclude-error.inc" line 1: Invalid line 'syntax error'
@


1.4
log
@make: add more context information to error messages

In case of a parse error or evaluation error, print the variable value
in addition to the variable name, to see the effects of previous
expression modifiers.

In nested make calls, print the current directory at the bottom of a
stack trace, as that information is otherwise hard to get in a parallel
build spanning multiple directories.
@
text
@d4 1
a4 1
make: stopped in unit-tests
@


1.3
log
@make: add more details to error message about invalid lines
@
text
@d2 1
@


1.3.2.1
log
@Sync with HEAD
@
text
@d1 1
a1 2
make: directive-dinclude-error.inc:1: Invalid line "syntax error"
	in directive-dinclude.mk:21
d3 1
a3 1
make: stopped making "all" in unit-tests
@


1.2
log
@tests/make: add a few more tests
@
text
@d1 1
a1 1
make: "directive-dinclude-error.inc" line 1: Invalid line type
@


1.1
log
@make(1): add tests for the various .include directives
@
text
@d1 4
a4 1
exit status 0
@