Lines Matching +refs:autotest +refs:mode +refs:map

4778 pre-C99 mode).  These can be tested with @code{#ifdef}.  A fallback to
7353 If the C compiler is not in ANSI C89 (ISO C90) mode by
7358 ANSI C89 mode if it handles function prototypes correctly.
7370 If the C compiler is not in C99 mode by default, try to add an
7374 considers the compiler to be in C99 mode if it handles @code{_Bool},
9494 If cross-compilation mode is enabled (this is the case if either the
9543 # We temporarily set cross-compile mode to force AC_COMPUTE_INT
11279 @item --mode=@var{octal-mode}
11280 @itemx -m @var{octal-mode}
11281 Set the mode of the non-traces output to @var{octal-mode}; by default
11447   m4sugar/m4sugar.m4f m4sugar/m4sh.m4f --mode 777 foo.m4
12353 @msindex{map}
12367 separating output with commas, this means that the map result can be
15204 Posix mode is buggy and causes @command{pdksh} to depart from Posix in
15558 even if it doesn't match the read/write mode that the file descriptor
15955 prints spurious quotes when in Posix mode:
15972 mode.  In the example below, the correct behavior is to have five
17038 compatibility mode and the @command{zsh} version is newer
17064 running in Posix mode.  Therefore, take care when exporting or unsetting
17066 mode.
17504 Solaris outputs 2, but Bash and Zsh (in @command{sh} emulation mode) output 1.
17761 But keep in mind that Zsh, even in Bourne shell emulation mode, performs
18065 native mode, asynchronous notification (@samp{set -b}) is enabled by
18066 default, and using @samp{emulate sh} to switch to Posix mode does not
18187 current user id compared to file owner and mode, as if by
18660 make the file unwritable, since it does not affect mode bits that
18661 correspond to bits in the file mode creation mask.  Second,
18663 implementation-specific option, not as a mode; Posix suggests
19206 temporary file name is to create a temporary directory with mode 700 and
20067 special emulation mode where features like pipes and redirections are
20124 When NetBSD or FreeBSD @command{make} are run in parallel mode, they will
20166 The BSD @command{make} implementations, when run in parallel mode,
20183 parallel mode, it implements the @code{@@} and @code{-} ``recipe
20250 mode for targets being updated by Solaris @command{dmake} and NetBSD
21754 cross-compilation mode.
21760 specified, enables cross-compilation mode.
21772 future.  So, to enter cross-compilation mode, use a command like this
24446 the enabling of cross-compilation mode.
24463 mode, so it doesn't run any tests that require execution.
24503 @command{configure} could even enter cross-compilation mode only
24508 Now, @command{configure} enters cross-compilation mode if and only if
24518 enters cross-compilation mode.  This is fragile.  Moreover, by the time
24529 enters cross-compilation mode.  The former interface, which
24768 @dfn{debug mode} (@pxref{testsuite Invocation}).  The automatic generation
25267 If the testsuite is run in verbose mode, with option @option{--verbose},
25268 EUnit is also run in verbose mode to output more details about
25301 In parallel mode, the standard input device of the testsuite script is
25308 Parallel mode requires the @command{mkfifo} command to work, and will be
25387 If the testsuite is run in parallel mode using @option{--jobs},
25398 test results will be colored.  With @samp{never}, color mode is turned
25520 AUTOTEST = $(AUTOM4TE) --language=autotest
26650 @c  LocalWords:  installcheck autotest indir Pixley Bothner Eichin Kerberos adl
26665 @c indent-tabs-mode: nil