|
Revision tags: perseant-exfatfs-base-20250801 netbsd-11-base
|
| #
1.13 |
|
30-Jun-2025 |
rillig |
tests/make: force expected lines to be listed in execution order
The diagnostics from the program to check the "expect" lines in the unit test files were hard to follow since the "out-of-order" lines were confusing. For out-of-order lines, state where they should be placed instead.
|
| #
1.12 |
|
12-Jun-2025 |
rillig |
make: add program name to stack traces from sub-makes
|
| #
1.11 |
|
12-Jun-2025 |
rillig |
make: add quotes to "in directory" line in stack traces
The other lines in stack traces use quotes as well.
|
| #
1.10 |
|
30-Mar-2025 |
rillig |
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.
|
| #
1.9 |
|
29-Aug-2024 |
rillig |
make: reduce line length in error messages
The error messages for deeply nested parse errors were hard to decipher, due to the large amount of text. Split these messages into individual lines, just as in the backtrace for .include files and .for loops. This unified backtrace makes the output more uniform.
|
| #
1.8 |
|
04-Jul-2024 |
rillig |
make: on error, print the targets to be made
This helps to understand situations with several nested sub-makes in varying directories.
|
| #
1.7 |
|
04-Jul-2024 |
rillig |
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.
|
|
Revision tags: perseant-exfatfs-base-20240630
|
| #
1.6 |
|
30-Jun-2024 |
rillig |
make: error out on syntax error in conditions in ':?then:else' modifier
The 'Error' function only reports errors but does not affect the exit status, the 'Parse_Error' function does, while providing more details to find the cause of the syntax error.
|
|
Revision tags: perseant-exfatfs-base
|
| #
1.5 |
|
10-Dec-2023 |
rillig |
branches: 1.5.2; make: remove redundant text from diagnostic about bad '?:' modifier
|
|
Revision tags: netbsd-10-1-RELEASE netbsd-10-0-RELEASE netbsd-10-0-RC6 netbsd-10-0-RC5 netbsd-10-0-RC4 netbsd-10-0-RC3 netbsd-10-0-RC2 netbsd-10-0-RC1 netbsd-10-base cjep_sun2x-base1 cjep_sun2x-base cjep_staticlib_x-base1 cjep_staticlib_x-base
|
| #
1.4 |
|
19-Apr-2021 |
rillig |
make: use straight quotes for error 'Bad conditional expression'
This diagnostic was supposed to be an error, see ApplyModifier_IfElse.
When such an error occurs while the makefiles are read, make stops with an error, as can be expected. But when such an error occurs later, after all makefiles have been read, the message is printed but make does not stop.
In lint mode (-dL), make stops in such a case. I didn't dare to make this the default behavior, out of fear of breaking existing build infrastructure, not only in NetBSD or pkgsrc, but also FreeBSD and other operating systems that use the bmake distribution, generated from the same source code.
|
| #
1.3 |
|
25-Jul-2020 |
rillig |
make(1): add test for undefined (or empty) variable in :? modifier
|
| #
1.2 |
|
01-May-2020 |
rillig |
usr.bin/make: fix test for late evaluated condition
|
| #
1.1 |
|
29-Apr-2020 |
rillig |
usr.bin/make: add test case for lazy conditions
|