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

1 2 3 4 5

  /src/usr.bin/make/unit-tests/
varname-makefile.exp 1 : In the end, MAKEFILE is /dev/null.
lint.exp 1 make: In the :@ modifier, the variable name "${:Ubar:S,b,v,}" must not contain a dollar
3 in command "@echo ${VAR:Uvalue:@${:Ubar:S,b,v,}@x${var}y@:Q}"
4 in target "mod-loop-varname" from lint.mk:22
varmod-loop-varname.exp 1 make: varmod-loop-varname.mk:17: In the :@ modifier, the variable name "${:Ubar:S,b,v,}" must not contain a dollar
3 make: varmod-loop-varname.mk:87: In the :@ modifier, the variable name "v$" must not contain a dollar
5 make: varmod-loop-varname.mk:93: In the :@ modifier, the variable name "v$$" must not contain a dollar
7 make: varmod-loop-varname.mk:99: In the :@ modifier, the variable name "v$$$" must not contain a dollar
10 make: stopped making "all" in unit-tests
opt-debug-errors-jobs.exp 5 *** In directory: <curdir>
10 make: stopped making "all" in unit-tests
15 *** In directory: <curdir>
20 make: stopped making "all" in unit-tests
27 *** In directory: <curdir>
34 make: stopped making "all" in unit-tests
39 *** In directory: <curdir>
44 make: stopped making "all" in unit-tests
49 *** In directory: <curdir>
54 make: stopped making "all" in unit-test
    [all...]
deptgt-delete_on_error.mk 3 # Tests for the special target .DELETE_ON_ERROR in dependency declarations,
7 # In compatibility mode, regular and phony targets are deleted, but precious
10 # In parallel mode, regular targets are deleted, while phony and precious
shell-ksh.mk 8 # This is only obvious in parallel mode since in compat mode,
14 # In parallel mode, the shell->noPrint command is filtered from
15 # the output, rather naively (in PrintOutput).
32 # In the Korn shell, "set +v" is set as the noPrint command.
34 # FIXME: Don't assume a newline character in PrintFilteredOutput.
posix-expansion.mk 5 # In POSIX mode, when expanding an expression containing modifiers, the
6 # modifiers specified in POSIX take precedence over the BSD-style modifiers.
varmod-loop-varname.mk 14 # Since var.c 1.907 from 2021-04-04, a '$' is no longer allowed in the
16 # expect+1: In the :@ modifier, the variable name "${:Ubar:S,b,v,}" must not contain a dollar
24 # ":::" is a very creative variable name, unlikely to occur in practice.
26 # be escaped in the modifiers, but not in the variable name, therefore
39 # In extreme cases, even the backslash can be used as variable name.
46 # The variable name can technically be empty, and in this situation
55 # than expected. In particular, it resolves _all_ variables from the scope,
56 # and not only the loop variable (in this case v).
66 # In the following example, the modifier ':@' expands the '$$' to '$'. Thi
    [all...]
varmod-undefined.mk 16 # .for word in one
25 # The expressions in the text of the :U modifier may be arbitrarily
33 # need to match pairwise. In the following example, the :S modifier uses '{'
45 # In the :U modifier, the backslash only escapes very few characters, all
48 # In condition string literals, the backslash always escapes the following
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.
dep-colon-bug-cross-file.mk 7 # In pass 1, there is a dependency group at the bottom of the file.
12 # After the file has been parsed completely, it is parsed again in pass 2.
13 # In this pass, another command is added to the "current dependency group",
17 # Oops, even worse. Running this test in a make from 2020-09-25 or earlier
24 # for this is that in MainParseArgs, the command line arguments were not
25 # properly copied before storing them in global variables.
recursive.mk 3 # In -dL mode, a variable may get expanded before it makes sense.
21 # 2020-08-06, when make ran in -dL mode, it reported: "Variable am__v_lt_ is
24 # Seen in pkgsrc/x11/libXfixes, and probably many more package that use
32 # When the variable is only parsed but not evaluated, bugs in nested
34 # therefore that's acceptable. In most practical cases, the missing
35 # brace would be detected directly in the line where it is produced.
shell-csh.mk 8 # This is only obvious in parallel mode since in compat mode,
14 # In parallel mode, the shell->noPrint command is filtered from
15 # the output, rather naively (in PrintOutput).
17 # Until 2020-10-03, the output in parallel mode was garbled because
35 # In the C shell, "unset verbose" is set as the noPrint command.
37 # FIXME: Don't assume a newline character in PrintFilteredOutput.
38 # expect: They chatted in the sy.
39 @echo 'They chatted in the sunset verbosely.'
varmod-ifelse.mk 14 # condition. In the below example it becomes:
24 # Evaluating the variable name lazily would require additional code in
34 # In a variable assignment, undefined variables are not an error.
41 # In a conditional directive, undefined variables are reported as such. In a
42 # ':?' modifier, though, the "variable name" is expanded first, and in that
44 # becomes the condition, in this case ' == ""', which is malformed because the
76 # If the "Bad condition" appears in a quoted string literal, the
80 # XXX: The left-hand side is enclosed in quotes. This results in Var_Pars
    [all...]
varmod-assign.mk 4 # assignments during evaluation, just like the = operator in C.
12 # In the following loop expression,
20 # In the following loop expression,
28 # In the following loop expression,
36 # In the following loop expression,
38 # with the modifier '::=', the last value is stored in the RAN variable.
44 # in the command line scope.
50 # used in practice.
81 # In this variant, it is not as obvious that the name of the
87 # In this variant, it is not as obvious that the name of th
    [all...]
varname.mk 7 # In a variable assignment, braces are allowed in the variable name, but they
14 # In expressions, the parser works differently. It doesn't treat
23 # In the above test, the variable name is constructed indirectly. Neither
29 # expect+2: Missing ")" in archive specification
30 # expect+1: Error in archive specification: "VAR"
39 # come from an external source, not the text that is parsed in the assignment
46 # All variable names of a scope are stored in the same hash table, using a
67 # other can be accessed. In this case, the shorter variable name is defined
68 # first to make it appear later in the bucket of the hash table
    [all...]
varmod-remember.mk 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.
15 ABC.global:= ${ABC} # is evaluated in the global scope
20 .if ${DEF} != "1=D 2=E 3=F" # is evaluated in the command line scope
25 # in the scope of the current evaluation, which meant that after the first
26 # ':_' modifier had been evaluated in command line scope, all further
27 # evaluations in global scope could not overwrite the variable '_' anymore
    [all...]
varname-dot-make-save_dollars.mk 8 # var-op-expand.mk for ':=' in general
25 # The reduction from 8 '$' to 4 '$' happens when ${VAR} is evaluated in the
55 # It's even possible to change the dollar interpretation in the middle of
65 # in the value of an expression, therefore .MAKE.SAVE_DOLLARS doesn't apply
73 # Undefining .MAKE.SAVE_DOLLARS does not have any effect, in particular it
82 # Undefining .MAKE.SAVE_DOLLARS does not have any effect, in particular it
93 # in indirect expressions.
95 # In this example, it affects the command in CMD itself, not the result of
112 # In the modifier ':@var@body@', .MAKE.SAVE_DOLLARS does not affect the body
    [all...]
varparse-undef-partial.mk 3 # When an undefined variable is expanded in a ':=' assignment, only the
5 # the remaining expression is evaluated. In edge cases this can lead to
36 # In contrast to the previous line, evaluating the original LIST again now
45 # It's difficult to decide what the best behavior is in this situation.
53 # not modified later. In this practical case, it does not matter whether the
56 # expression ${COMPILER} would be expanded several times, but in this simple
cond-eof.mk 10 # In the following conditions, ${SIDE_EFFECT} is the position of the first
14 # operation. Still, it is easy to avoid evaluating these expressions, just in
  /src/share/doc/psd/20.ipctut/
socketpair.c 6 .\" Redistribution and use in source and binary forms, with or without
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in the
21 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
25 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
26 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
36 #define DATA1 "In Xanadu, did Kublai Khan . . ."
43 * send messages in both directions.
  /src/sys/external/bsd/acpica/dist/resources/
rsxface.c 11 * Redistribution and use in source and binary forms, with or without
17 * 2. Redistributions in binary form must reproduce at minimum a disclaimer
34 * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
38 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
40 * IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
56 #define ACPI_COPY_FIELD(Out, In, Field) ((Out)->Field = (In)->Field)
57 #define ACPI_COPY_ADDRESS(Out, In) \
58 ACPI_COPY_FIELD(Out, In, ResourceType); \
59 ACPI_COPY_FIELD(Out, In, ProducerConsumer);
    [all...]
  /src/sys/external/bsd/acpica/dist/utilities/
utmisc.c 11 * Redistribution and use in source and binary forms, with or without
17 * 2. Redistributions in binary form must reproduce at minimum a disclaimer
34 * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
38 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
40 * IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
57 * PARAMETERS: Id - The HID/CID in string format
148 } In;
154 In.Value = Value;
156 Out.Bytes[0] = In.Bytes[3];
157 Out.Bytes[1] = In.Bytes[2]
    [all...]
  /src/sys/external/bsd/compiler_rt/dist/lib/fuzzer/dataflow/
DataFlow.cpp 38 // # Print all instrumented functions. llvm-symbolizer must be present in PATH
78 // TODO(kcc): this is pretty ugly and may break in lots of ways.
79 // We'll need to make a proper in-process symbolizer work with DFSan.
134 FILE *In = fopen(Input, "r");
135 assert(In);
136 fseek(In, 0, SEEK_END);
137 InputLen = ftell(In);
138 fseek(In, 0, SEEK_SET);
140 size_t NumBytesRead = fread(Buf, 1, InputLen, In);
143 fclose(In);
    [all...]
  /src/distrib/mac68k/miniroot/
install.md 11 # Redistribution and use in source and binary forms, with or without
16 # 2. Redistributions in binary form must reproduce the above copyright
17 # notice, this list of conditions and the following disclaimer in the
23 # PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
27 # INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
29 # ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
54 # 2048 is the size in DEV_BIZE blocks
133 This program is designed to help you install NetBSD on your system in a
138 In particular, you will need to know some reasonably detailed
152 Default answers are displayed in brackets after the questions
    [all...]
  /src/sys/conf/
copts.mk 56 # In file included from ./machine/endian.h:3,
59 # In function 'le32dec',
64 # /home/riastradh/netbsd/current/src/sys/sys/endian.h:228:1: note: in expansion of macro '__GEN_ENDIAN_DEC'
67 # /home/riastradh/netbsd/current/src/sys/crypto/aes/aes_bear64.c: In function 'aesbear64_cbc_dec.part.0':
68 # /home/riastradh/netbsd/current/src/sys/crypto/aes/aes_bear64.c:229:59: note: at offset 48 into object 'in' of size [0, 16]
69 # 229 | aesbear64_cbc_dec(const struct aesdec *dec, const uint8_t in[static 16],

Completed in 39 milliseconds

1 2 3 4 5