The NetBSD Project

CVS log for src/usr.bin/make/unit-tests/include-main.exp

[BACK] Up to [cvs.NetBSD.org] / src / usr.bin / make / unit-tests

Request diff between arbitrary revisions


Default branch: MAIN


Revision 1.13 / (download) - annotate - [select for diffs], Thu Jun 1 20:56:35 2023 UTC (5 days, 4 hours ago) by rillig
Branch: MAIN
CVS Tags: HEAD
Changes since 1.12: +5 -5 lines
Diff to previous 1.12 (colored)

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.

Revision 1.12 / (download) - annotate - [select for diffs], Thu Jan 19 23:26:14 2023 UTC (4 months, 2 weeks ago) by rillig
Branch: MAIN
Changes since 1.11: +8 -8 lines
Diff to previous 1.11 (colored)

tests/make: rename files that are not test cases

Revision 1.11 / (download) - annotate - [select for diffs], Sun Jan 9 11:43:58 2022 UTC (16 months, 3 weeks ago) by rillig
Branch: MAIN
CVS Tags: netbsd-10-base, netbsd-10
Changes since 1.10: +0 -1 lines
Diff to previous 1.10 (colored)

make: remove redundant lines from stack traces

These lines repeated the information from the .for loop line above them.

Revision 1.10 / (download) - annotate - [select for diffs], Sat Jan 8 23:52:26 2022 UTC (16 months, 3 weeks ago) by rillig
Branch: MAIN
Changes since 1.9: +3 -3 lines
Diff to previous 1.9 (colored)

make: add details about .for loop variables to stack traces

The stack traces are enabled with the debug logging option '-dp'.

Revision 1.9 / (download) - annotate - [select for diffs], Sat Jan 8 23:41:43 2022 UTC (16 months, 3 weeks ago) by rillig
Branch: MAIN
Changes since 1.8: +2 -1 lines
Diff to previous 1.8 (colored)

make: fix stack traces in -dp mode (since 2021-01-26)

Previously, the stack traces omitted some lines that seemed to be
redundant.  As a result, the stack traces contained confusing line
numbers.

Revision 1.8 / (download) - annotate - [select for diffs], Tue Dec 28 15:49:00 2021 UTC (17 months, 1 week ago) by rillig
Branch: MAIN
Changes since 1.7: +2 -2 lines
Diff to previous 1.7 (colored)

make: make debug logging a bit more human-friendly

The previous log format "ParseReadLine (%d): '%s'" focused on the
implementation, it was not immediately obvious to a casual reader that
the number in parentheses was the line number.  Additionally, having
both a colon and quotes in a log message is uncommon.  The quotes have
been added in parse.c 1.127 from 2007-01-01.

The new log format "Parsing line %d: %s" is meant to be easier readable
by humans.  The quotes are not needed since ParseReadLine always strips
trailing whitespace, leaving no room for ambiguities.  The other log
messages follow common punctuation rules, which makes the beginning of
the line equally unambiguous.  Before var.c 1.911 from 2021-04-05,
variable assignments were logged with the format "%s:%s = %s", without a
space after the colon.

Revision 1.7 / (download) - annotate - [select for diffs], Sun Apr 4 10:13:09 2021 UTC (2 years, 2 months ago) by rillig
Branch: MAIN
CVS Tags: cjep_sun2x-base1, cjep_sun2x-base, cjep_sun2x, cjep_staticlib_x-base1, cjep_staticlib_x-base, cjep_staticlib_x
Changes since 1.6: +1 -1 lines
Diff to previous 1.6 (colored)

make: remove filler word 'Do' from function names for parsing

No functional change, except for debug logging.

Revision 1.6 / (download) - annotate - [select for diffs], Tue Jan 26 23:44:56 2021 UTC (2 years, 4 months ago) by rillig
Branch: MAIN
Changes since 1.5: +8 -1 lines
Diff to previous 1.5 (colored)

make(1): in -dp mode, print stack trace with each diagnostic

This makes it easier to track down where a warning or an error
originated from.  This information could be further enriched for .for
loops, to also include the variable names and their values.  For now,
it's good enough to replace the large comment describing how a stack
trace _could_ be generated with actual code that implements that idea.

The syntax of the locations is <filename>:<lineno>, which intentionally
differs from the traditional "<filename>" line <lineno>, since the
former is more widely supported by editors and IDEs.

Having this stacktrace information is especially intended for
complicated systems built upon make, such as pkgsrc.

Revision 1.5 / (download) - annotate - [select for diffs], Mon Sep 14 19:59:47 2020 UTC (2 years, 8 months ago) by rillig
Branch: MAIN
Changes since 1.4: +2 -2 lines
Diff to previous 1.4 (colored)

make(1): describe how Parse_Error might print stack traces

In deeply nested include chains and .for loops this may be a useful
feature.  It's a little tricky to generate an intuitive stack trace,
though not impossible.  This explanation also serves as a detailed
documentation about how the .include and .for directives are
implemented.

Revision 1.4 / (download) - annotate - [select for diffs], Sat Sep 5 18:18:05 2020 UTC (2 years, 9 months ago) by rillig
Branch: MAIN
Changes since 1.3: +6 -6 lines
Diff to previous 1.3 (colored)

make(1): fix .INCLUDEDFROMDIR/.INCLUDEDFROMFILE

Revision 1.3 / (download) - annotate - [select for diffs], Sat Sep 5 18:13:47 2020 UTC (2 years, 9 months ago) by rillig
Branch: MAIN
Changes since 1.2: +6 -2 lines
Diff to previous 1.2 (colored)

make(1): add test for .INCLUDEDFILE combined with .for loops

The .for loops are implemented as a special kind of .include, therefore
they affect the .INCLUDEDFROM variable.

Revision 1.2 / (download) - annotate - [select for diffs], Sat Sep 5 16:59:19 2020 UTC (2 years, 9 months ago) by rillig
Branch: MAIN
Changes since 1.1: +5 -5 lines
Diff to previous 1.1 (colored)

make(1): make test for .INCLUDEDFROMDIR simpler

The .info and .warning directives provide exactly the early expansion
that this test needs.  No more .for for getting a snapshot of a
variable.

Revision 1.1 / (download) - annotate - [select for diffs], Sun May 17 12:36:26 2020 UTC (3 years ago) by rillig
Branch: MAIN

usr.bin/make: demonstrate actual behavior of .INCLUDEDFROMFILE

This form allows you to request diff's between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.




CVSweb <webmaster@jp.NetBSD.org>