|
Revision tags: perseant-exfatfs-base-20250801 netbsd-11-base
|
| #
1.16 |
|
28-Jun-2025 |
rillig |
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.
|
| #
1.15 |
|
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.14 |
|
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.
|
|
Revision tags: perseant-exfatfs-base-20240630 perseant-exfatfs-base
|
| #
1.13 |
|
19-Oct-2023 |
rillig |
branches: 1.13.2; tests/make: clean up, explain and reorganize several tests
|
| #
1.12 |
|
04-Mar-2023 |
rillig |
tests/make: use proper variable names in short-circuit test
The previous variable names V42, V66, iV1 and iV2 didn't carry enough information to be readily readable, making the test hard to understand.
Rename the variables to be more expressive. While here, properly explain what happened behind the scenes in 2020 and how the evaluation of conditions was fixed after discovering the actual cause of the unexpected error messages.
|
|
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.11 |
|
01-Dec-2020 |
rillig |
make(1): adjust condition descriptions in test cond-short
Before, the conditions in the output had been expanded, which made them illegible. The expanded conditions were unrealistic as well since the evaluation flags differ between a condition and normal evaluation (VARE_WANTRES, VARE_UNDEFERR).
|
| #
1.10 |
|
09-Jul-2020 |
sjg |
compare_expression: return after fetch lhs and rhs if !doEval
Otherwise we end up throwing warings/errors for valid conditionals due to not expanding variables fully.
Add tests to catch this.
Reviewed by: rillig
|
| #
1.9 |
|
02-Jul-2020 |
rillig |
make(1): fix unnecessary evaluation of variables in :@var@ modifier
|
| #
1.8 |
|
02-Jul-2020 |
rillig |
make(1): fix unnecessary evaluation for :S :C := modifiers
|
| #
1.7 |
|
02-Jul-2020 |
rillig |
make(1): demonstrate some more cases for unintended evaluation
|
| #
1.6 |
|
02-Jul-2020 |
rillig |
make(1): fix unnecessary evaluation of :M and :N modifiers
|
| #
1.5 |
|
02-Jul-2020 |
rillig |
make(1): demonstrate another unintended variable evaluation
|
| #
1.4 |
|
02-Jul-2020 |
rillig |
make(1): fix edge case for evaluating unnecessary conditions
|
| #
1.3 |
|
02-Jul-2020 |
rillig |
make(1): demonstrate another unnecessary condition evaluation
|
| #
1.2 |
|
28-Jun-2020 |
rillig |
make(1): fix evaluation of unreachable conditions
Since 2015-10-11, make had evaluated unreachable conditions even though the manual page said it didn't.
|
| #
1.1 |
|
28-Jun-2020 |
rillig |
make(1): demonstrate bug when evaluating conditions
|