| /src/usr.bin/make/unit-tests/ |
| order.exp | 1 Making the.c
2 Making the.h
3 Making the.o from the.h the.c
|
| order.mk | 4 # The explicit dependency the.o: the.h will make us examine the.h
5 # the .ORDER will prevent us building it immediately,
6 # we should then examine the.c rather than stop.
10 all: the.o
12 .ORDER: the.c the.h
14 the.c the.h
[all...] |
| directive-ifnmake.exp | 1 Don't forget to run the tests (1)
2 Running the tests
|
| varmod-exclam-shell.mk | 3 # Tests for the :!cmd! variable modifier, which evaluates the modifier
4 # argument, independent of the value or the name of the original variable.
10 # The output is truncated at the first null byte.
12 # Truncating the output is not necessarily intended but may also be a side
13 # effect from the implementation. Having null bytes in the output of
[all...] |
| sh.mk | 3 # Tests for running shell commands from the targets, or from the != variable
4 # assignment operator or the :sh variable modifier.
7 # var-op-shell.mk for the assignment operator '!='
|
| varname-makefile.exp | 1 : In the end, MAKEFILE is /dev/null.
|
| varmod-quote-dollar.mk | 3 # Tests for the :q variable modifier, which quotes the string for the shell
7 # The newline and space characters at the beginning of this string are passed
8 # to the child make. When the child make parses the variable assignment, it
9 # discards the leading space characters.
|
| varmod-tail.mk | 3 # Tests for the :T variable modifier, which returns the basename of each of
4 # the words in the variable value.
7 # If the ':T' is not directly followed by a delimiting ':' or '}', the
|
| hanoi-include.exp | 1 Move the upper disk from stack A to stack C.
2 Move the upper disk from stack A to stack B.
3 Move the upper disk from stack C to stack B.
4 Move the upper disk from stack A to stack C.
5 Move the upper disk from stack B to stack A.
6 Move the upper disk from stack B to stack C.
7 Move the upper disk from stack A to stack C.
8 Move the upper disk from stack A to stack B.
9 Move the upper disk from stack C to stack B.
10 Move the upper disk from stack C to stack A
[all...] |
| varmod-remember.mk | 3 # Tests for the :_ modifier, which saves the current expression value
4 # in the _ variable or another, to be used later again.
7 # The ':_' modifier is typically used in situations where the value of an
8 # expression is needed at the same time as a sequence of numbers. In these
9 # cases, the value of the expression is saved in the temporary variable '_',
10 # from where it is taken later in the same expression
[all...] |
| varmod-loop-varname.mk | 3 # Tests for the first part of the variable modifier ':@var@...@', which
4 # contains the variable name to use during the loop.
6 # Force the test results to be independent of the default value of this
7 # setting, which is 'yes' for NetBSD's usr.bin/make but 'no' for the bmake
12 # Before 2021-04-04, the name of the loop variable could be generated
14 # Since var.c 1.907 from 2021-04-04, a '$' is no longer allowed in the
[all...] |
| suff-main.mk | 3 # Demonstrate that an inference rule is considered the main target if its
4 # suffixes are not known at the point of declaration.
9 # At this point, the target '.1.2' is a normal target.
10 # Since it is the first target in the first dependency declaration,
11 # it becomes the main target.
18 # Declaring both '.1' and '.2' as suffixes turns the '.1.2' target into an
20 # a candidate for the main target. Therefore the next target is selected as
21 # the main target, which in this case is 'next-main'
[all...] |
| varmod-match-escape.mk | 3 # As of 2020-08-01, the :M and :N modifiers interpret backslashes differently,
4 # depending on whether there was an expression somewhere before the
7 # Apart from the different and possibly confusing debug output, there is no
8 # difference in behavior. When parsing the modifier text, only \{, \} and \:
9 # are unescaped, and in the pattern matching these have the same meaning as
10 # their plain variants '{', '}' and ':'. In the pattern matching from
23 # XXX: As of 2020-11-01, when an escaped ':' occurs before the
24 # expression, the whole modifier text is subject to unescaping '\:' to ':',
25 # before the expression is expanded. This means that the '\:' i
[all...] |
| deptgt-silent.mk | 3 # Tests for the special target .SILENT in dependency declarations.
8 @echo 'This is not echoed because of the @.'
9 # Without the .SILENT, the following command would be echoed.
10 echo 'This is not echoed because of the .SILENT.'
12 # Demonstrate that the .SILENT only applies to the particular target.
|
| varmod-ifelse.mk | 3 # Tests for the ${cond:?then:else} variable modifier, which evaluates either
4 # the then-expression or the else-expression, depending on the condition.
6 # The modifier was added on 1998-04-01.
8 # Until 2015-10-11, the modifier always evaluated both the "then" and the
13 # The variable name of the expression is expanded and then taken as th
[all...] |
| varmod-loop-delete.mk | 3 # Tests for the variable modifier ':@', which as a side effect allows to
6 # A side effect of the modifier ':@' is that the loop variable is created as
7 # an actual variable in the current evaluation scope (Command/Global/target),
8 # and at the end of the loop, this variable is deleted. Since var.c 1.204
12 # See Var_Parse, comment 'the value of the variable must not change'.
14 # Set up the variable that deletes itself when it is evaluated.
15 VAR= ${:U:@VAR@@} rest of the valu
[all...] |
| varmod-to-abs.mk | 3 # Tests for the :tA variable modifier, which returns the absolute path for
4 # each of the words in the variable value.
8 # Between 2016-06-03 and 2020-11-14, it was possible to trick the :tA modifier
10 # variable with the same name as the path that is to be resolved. There were
11 # a few restrictions though: The "redirected" path had to start with a slash,
15 # keeping the cache, just like the GNode for global variables
[all...] |
| varname-dollar.mk | 3 # Tests for the expression "$$", which looks as if it referred to a variable,
6 # If there really were a special variable named '$', the expressions ${${DOLLAR}}
7 # and $$ would always expand to the same value.
9 # Using the dollar sign in variable names is tricky and not recommended.
10 # To see that using this variable indeed affects the variable '$', run the
11 # test individually with the -dv option.
14 # At this point, the variable '$' is not defined. Therefore the second line
21 # Now overwrite the '$' variable to see whether '$$' really expands to tha
[all...] |
| dep-colon.mk | 3 # Tests for the : operator in dependency declarations.
7 # In a dependency declaration line, there may be a shell command after the
14 # The semicolon for separating the sources from the creation commands must
15 # appear at the top-level. The semicolons inside the :S;1;2; modifier are
16 # skipped when looking for the semicolon that separates the sources fro
[all...] |
| depsrc-precious.mk | 3 # Tests for the special source .PRECIOUS in dependency declarations, which
4 # is only relevant if the commands for the target fail or are interrupted.
5 # In such a case, the target file is usually removed, to avoid having
6 # half-finished files with a timestamp suggesting the file were up-to-date.
8 # For targets marked with .PRECIOUS, the target file is not removed.
9 # The author of the makefile is then responsible for avoiding the above
10 # situation, in which the target would be wrongly considered up-to-date
[all...] |
| opt-ignore.mk | 3 # Tests for the -i command line option, which ignores the exit status of the
4 # shell commands, and just continues with the next command, even from the same
9 # Why are the "Error code" lines all collected at the bottom of the output
10 # file, where they cannot be related to the individual shell commands that
|
| deptgt-begin-fail-indirect.mk | 4 # This stops make immediately and does not build the main targets.
6 # Between 2005-05-08 and 2020-11-24, a failing dependency of the .BEGIN node
7 # would not stop make from running the main targets. In the end, the exit
|
| /src/lib/libc/time/ |
| tzcode2netbsd | 6 # Convert an extracted tzcode distribution into the format suitable
7 # for importing it into the NetBSD source tree.
30 echo you can find the current version in the Makefile
31 echo we don't use this script anymore to import, but diff against the
|
| /src/sys/arch/sun2/sun2/ |
| locore.s | 5 * The Regents of the University of California. All rights reserved.
8 * the Systems Programming Group of the University of Utah Computer
12 * modification, are permitted provided that the following conditions
14 * 1. Redistributions of source code must retain the above copyright
15 * notice, this list of conditions and the following disclaimer.
16 * 2. Redistributions in binary form must reproduce the above copyright
17 * notice, this list of conditions and the following disclaimer in the
[all...] |
| /src/sys/arch/sun68k/stand/ |
| README | 3 The sun bootblocks are split into two parts: a small 1st-level program that
4 gets written right after the superblock in a partition (and is hence limited
6 in the filesystem proper.
8 The 1st-level program is loaded into memory by the PROM. It loads the second
10 into it by the `installboot' program. The prototype code for the 1st-level
13 The 2nd-level program (`ufsboot') is normally installed in the root F
[all...] |
