HomeSort by: relevance | last modified time | path
    Searched refs:An (Results 1 - 25 of 47) sorted by relevancy

1 2

  /src/tests/sbin/ifconfig/
t_random_garbage.sh 31 echo $(od -An -N2 -i /dev/urandom | sed 's/ //')
  /src/usr.bin/make/unit-tests/
opt-debug-var.mk 31 # An expression for a variable with a single-character ordinary name.
37 # An expression for a target-specific variable with a single-character name.
depsrc-optional.mk 15 : An optional leaf node is not executed.
directive-else.mk 5 # Since 2020-11-13, an '.else' followed by extraneous text generates a parse
8 # Since 2020-12-15, an '.else' followed by extraneous text always generates
27 # An .else without a corresponding .if is an error.
39 . info After an extra .else, everything is skipped.
42 # An .else may have a comment. This comment does not count as an argument,
48 # An expression does count as an argument, even if it is empty.
cond-token-string.mk 12 # an expression based on an undefined variable.
28 # comparison in an .if directive must be either an expression, a
69 # expect+1: An undefined variable in quotes expands to an empty string, which then evaluates to false.
70 . info An undefined variable in quotes expands to an empty string, which $\
84 # expect+1: An empty variable evaluates to false.
85 . info An empty variable evaluates to false
    [all...]
cond-op-parentheses.mk 42 # An unbalanced opening parenthesis is a parse error.
50 # An unbalanced closing parenthesis is a parse error.
sh-leading-hyphen.mk 17 # An undefined variable expands to an empty string, without warning.
cond-token-var.mk 5 # Note the fine distinction between a variable and an expression.
6 # A variable has a name and a value. To access the value, one writes an
40 # A defined variable may appear as an expression of its own.
44 # An undefined variable on its own generates a parse error.
49 # The :U modifier turns an undefined expression into a defined expression.
72 # A defined variable may appear as an expression of its own.
76 # An undefined variable without a comparison operator generates a parse error.
104 # The left-hand side of a comparison must not be an unquoted word.
109 # The left-hand side of a comparison must not be an unquoted word.
114 # The left-hand side of a comparison must not be an unquoted word
    [all...]
varparse-errors.mk 16 INDIRECT= An ${:Uindirect} value.
18 REF_UNDEF= A reference to an ${UNDEF}undefined variable.
20 ERR_UNCLOSED= An ${UNCLOSED expression.
22 ERR_BAD_MOD= An ${:Uindirect:Z} expression with an unknown modifier.
24 ERR_EVAL= An evaluation error ${:Uvalue:C,.,\3,}.
26 # In a conditional, an expression that is not enclosed in quotes is
30 .if ${REF_UNDEF} != "A reference to an undefined variable."
36 # in an error message and a non-zero exit status.
45 # in an error message and a non-zero exit status
    [all...]
comment.mk 42 # This comment ends with 2 backslashes. An even number of backslashes does
64 # An odd number of backslashes makes a line continuation, \\\
varmod-head.mk 46 # The head of "/" was an empty string before 2020.07.20.14.50.41, leading to
53 _!= echo "The modifier ':H' generates an empty word." 1>&2; echo
58 # An empty list is split into a single empty word.
var-recursive.mk 4 # evaluated, as that would lead to an endless loop.
8 DIRECT= ${DIRECT} # Defining a recursive variable is not an error.
11 . info <${DIRECT}> # But expanding such a variable is an error.
29 # An expression with modifiers is skipped halfway. This can lead to wrong
varmod-indirect.mk 37 # An indirect variable that evaluates to the empty string is allowed.
45 # If an expression for an indirect modifier evaluates to anything else than an
59 # An indirect modifier can be followed by other modifiers, no matter if the
60 # indirect modifier evaluates to an empty string or not.
87 # have been an unknown modifier anyway) and the ":tl" modifier is applied.
93 # The indirect modifier can also replace an ':L' modifier, which allows for
98 M_ExpandVar= # an empty modifier
136 # An undefined expression without any modifiers expands to an empty string
    [all...]
cond-cmp-string.mk 17 # This one is not enclosed in quotes and thus generates an error message.
23 # An expression that occurs on the left-hand side of the comparison must be
27 # starting point for an expression. Applying the :U modifier to such an
66 # An expression can be enclosed in double quotes.
72 # characters " \t!=><" directly after an expression in a string literal
cond-cmp-unary.mk 27 # The empty string may come from an expression.
35 # An expression that is not surrounded by quotes is interpreted
41 # A non-zero number from an expression evaluates to true.
49 # whitespace before testing for the end. This was probably an oversight in
directive-export.mk 34 # makefile, when VARNAMES was an empty list.
35 # expect+1: warning: .export requires an argument.
38 # An empty argument means no additional variables to export.
46 # exported first, ending in an endless loop. To avoid this endless loop,
cond-undef-lint.mk 17 # An expression based on a defined variable is fine.
32 # an expression that is always defined, using the :U modifier.
42 # refers to an undefined variable, thus an error message.
61 # nested variables into empty strings, as an equivalent to the :U modifier.
66 # an error message, and it doesn't do so, since 2020-09-14.
deptgt.mk 33 # It doesn't matter whether the empty string is generated by an
42 # An expression based on an undefined variable is allowed on both sides of
varmod-assign.mk 14 # operator '?=' only has an effect for the first time, therefore the variable
43 # When a '::=' modifier is evaluated as part of an .if condition, it happens
101 # An 'x' after that is an invalid modifier.
106 # When parsing an assignment operator fails because the operator is
137 # The assignment modifier can be used in an expression that is
147 # Before var.c 1.888 from 2021-03-15, an expression using the modifier '::='
172 # Conditional directives are evaluated in command line scope. An assignment
201 # The commands of a target are evaluated in target scope. An assignment
var-op-default.mk 21 # An empty variable is defined, therefore the '?=' operator does nothing.
29 # variables. This is not entirely true. Instead, each occurrence of an
32 # there is never an actual variable named 'i' involved.
varmod-undefined.mk 15 # This is how an expanded .for loop looks like.
51 # In both contexts, \n is an escaped letter n, not a newline; that's what
59 # An expression enclosed in quotes may be based on an undefined variable.
65 # that it originated from an undefined variable, and the :U modifier can
directive-for-errors.mk 32 # Before for.c 1.173 from 2023-05-08, the variable name could be an arbitrary
49 # since this would end up in an endless loop, consuming 0 of the 3 values in
70 # comes from an expanded expression or from a syntactically empty line.
83 # An error in the items skips the body of the loop.
  /src/sys/external/gpl2/dts/dist/arch/arm/boot/dts/
kirkwood-nas2big.dts 36 * A NAND flash is used instead of an SPI flash for
45 * An I2C fan controller (GMT G762) is used but alarm is
92 * An external I2C RTC (Dallas DS1337S+) is used. This allows
93 * to power-up the board on an RTC alarm. The external RTC can
am335x-bonegreen-wireless.dts 117 /* use a gpio hog to force this pin low. An alternative may be adding */
118 /* an external pulldown on U21 pin 4. */
  /src/tests/sbin/sysctl/
t_random_garbage.sh 33 echo $(od -An -N2 -i /dev/urandom | sed 's/ //')

Completed in 15 milliseconds

1 2