/freebsd-13-stable/contrib/bmake/unit-tests/ |
H A D | varname-dot-newline.exp | 1 make: "varname-dot-newline.mk" line 16: The .newline variable can be overwritten. Just don't do that.
|
H A D | varname-dot-newline.mk | 5 # Contrary to the special variable named "" that is used in expressions like 7 # modification. Nobody exploits that though. 16 . info The .newline variable can be overwritten. Just don't do that.
|
H A D | unexport.mk | 11 # Until 2020-08-08, Var_UnExport had special handling for '\n', that code 12 # was not reachable though. At that point, backslash-newline has already
|
H A D | forloop.mk | 17 CFL= -I/this -I"This or that" -Ithat "-DTHIS=\"this and that\"" 39 # that a newline ever occurred. 53 { echo "Oops that should have failed!"; exit 1; } || echo OK
|
H A D | varmod-match.mk | 3 # Tests for the :M variable modifier, which filters words that match the 12 # Only keep words that start with an uppercase letter. 17 # Only keep words that start with a character other than an uppercase letter. 22 # Only keep words that don't start with s and at the same time end with 25 # This test case ensures that the negation from the first character class
|
H A D | varname-dot-parsedir.mk | 4 # of the file that is currently parsed. 6 # The .PARSEDIR may be absolute or relative, therefore there is not much that 13 # Not that anyone would ever want to do this, but there's code in parse.c, 14 # function PrintLocation, that explicitly handles this situation. 30 # There is absolutely no point in faking the location of the file that is
|
H A D | cmdline-redirect-stdin.mk | 3 # Demonstrate that the '!=' assignment operator can read individual lines 6 # This edge case is an implementation detail that has no practical 23 # is actually specified by POSIX, which says that "The read utility shall
|
H A D | dotwait.mk | 9 # that the tests are run one by one, with parallelism 20 # * If it's expected that two or more targets may be made in parallel, 23 # * If it's expected that two or more targets should be made in sequence 24 # then the target names will differ in numeric components, such that 30 # are converted to ".*". Two targets that are expected to 31 # be made in parallel will thus print the same strings, so that the
|
H A D | counter-append.mk | 6 # This works since 2020-09-23. Before that, the counter ended up at having 8 # The cause for this surprising behavior was that the ::= variable modifiers
|
H A D | counter.mk | 6 # This works since 2020-09-23. Before that, the counter ended up at having 8 # The cause for this surprising behavior was that the ::= variable modifiers
|
H A D | directive-export.mk | 18 # During that, its value is expanded, just like almost everywhere else. 24 # Undefining a variable that has been exported implicitly removes it from
|
H A D | recursive.mk | 7 # The purpose of evaluating that variable early was just to detect 9 # variable value without VARE_WANTRES for that purpose. 11 # Seen in pkgsrc/x11/libXfixes, and probably many more package that use 33 # therefore that's acceptable. In most practical cases, the missing
|
H A D | var-recursive.mk | 3 # Tests for variable expressions that refer to themselves and thus 25 # The chain of variables that refer to each other may be long. 32 # The variable refers to itself, but only in the branch of a condition that 41 # name. Ensure that these are checked as well.
|
H A D | varname-dot-parsefile.mk | 4 # of the file that is currently parsed. 11 # Not that anyone would ever want to do this, but there's code in parse.c, 12 # function PrintLocation, that explicitly handles this situation. 25 # There is absolutely no point in faking the location of the file that is
|
/freebsd-13-stable/contrib/dialog/samples/ |
H A D | checklist12 | 19 Dog:No, that's not my dog.:ON 20 Orange:Yeah, that's juicy.:off
|
/freebsd-13-stable/contrib/bmake/mk/ |
H A D | target-flags.mk | 31 # It is important that target-flags.mk is included after other 32 # macro files and that target specific flags that may reference 33 # _$v are set after that. 35 # Only works with a make(1) that does nested evaluation correctly. 44 # This file is provided in the hope that it will 47 # use this file is hereby granted provided that
|
H A D | libnames.mk | 5 # This file is provided in the hope that it will 8 # use this file is hereby granted provided that
|
H A D | host.libnames.mk | 5 # This file is provided in the hope that it will 8 # use this file is hereby granted provided that
|
H A D | dpadd.mk | 5 # This file is provided in the hope that it will 8 # use this file is hereby granted provided that 18 # This makefile manages a number of variables that simplify 24 # List of LIB* that we will actually link with 26 # DPLIBS is a short-cut to ensure that DPADD and LDADD are 29 # DPADD List of LIB* that should already be built. 32 # List of LIB* that we want headers from, we do *not* 33 # require that such libs have been built. 64 # only add -I${SRC_${__lib:T:R}}/h on the basis that 74 # Since we can safely assume that [all...] |
H A D | whats.mk | 5 # This file is provided in the hope that it will 8 # use this file is hereby granted provided that 18 # so that the build location can be seen from a core file. 31 # a unique name that won't conflict with anything
|
/freebsd-13-stable/cddl/usr.sbin/dtrace/tests/tools/ |
H A D | gentest.sh | 10 excludes: A shell script which defines test cases that are to be skipped,
|
/freebsd-13-stable/stand/lua/ |
H A D | hook.lua | 7 -- modification, are permitted provided that the following conditions 35 -- Register a hook type; these are the names that hooks may be registered for. 36 -- It is expected that modules will register all of their hook types upon 41 -- with the name of the module that registered them. They would also ideally 42 -- describe an action that may or may not match a function name. 60 -- Takes a hooktype and runs all functions associated with that specific hook 61 -- type in the order that they were registered in. This ordering should likely 70 -- catch that as soon as possible.
|
/freebsd-13-stable/crypto/openssl/ |
H A D | NOTES.PERL | 17 differ, and you may have to check that you do get the core modules 28 other features that didn't exist in core Perl before that version. 33 There are a number of build targets that can be viewed as "Windows". 36 one that matches build environment. For example, if you will build 59 appeared in Perl 5.13.4, because that version was 85 for the module name and to install the package that comes up. 103 Note that this runs all the tests that the module to be installed 106 were successful. Should that happe [all...] |
/freebsd-13-stable/contrib/llvm-project/compiler-rt/lib/xray/ |
H A D | xray_trampoline_arm.S | 15 @ Assume that "q" part of the floating-point registers is not used 31 @ r1=0 means that we are tracing an entry event 45 @ Assume that d1-d7 are not used for the return value. 46 @ Assume that "q" part of the floating-point registers is not used for the 63 @ 1 means that we are tracing an exit event 78 @ Assume that "q" part of the floating-point registers is not used 94 @ r1=2 means that we are tracing a tail exit event 95 @ But before the logging part of XRay is ready, we pretend that here a
|
/freebsd-13-stable/cddl/contrib/opensolaris/cmd/dtrace/test/tst/common/pragma/ |
H A D | tst.temporal2.ksh | 51 * Use two enablings of the same probe, so that cpu 0 will always 54 * that we record the timestamp, because chill() causes the
|