Lines Matching +refs:autotest +refs:mode +refs:syntax +refs:table
638 file with a vastly simpler and more powerful syntax than that of a plain
710 whenever shared libraries are needed, and you need not know its syntax.
1279 Warnings about `syntax' are enabled by default, and the environment
1282 had passed `--warnings syntax,$WARNINGS,CATEGORY'. To disable the
1463 `syntax'
1478 Warnings about `syntax' are enabled by default, and the environment
1481 had passed `--warnings syntax,$WARNINGS,CATEGORY'. To disable the
3886 possibly as `__va_copy' (e.g., `gcc' in strict pre-C99 mode).
5765 If the C compiler is not in ANSI C89 (ISO C90) mode by default,
5770 mode if it handles function prototypes correctly.
5779 If the C compiler is not in C99 mode by default, try to add an
5783 modes. It considers the compiler to be in C99 mode if it handles
5963 If the C compiler supports GCC's `typeof' syntax either directly or
7201 `AC_LANG_SOURCE', yet still want to avoid a syntax warning from
7416 To check for a syntax feature of the current language's (*note Language
7524 If cross-compilation mode is enabled (this is the case if either
7570 # We temporarily set cross-compile mode to force AC_COMPUTE_INT
7617 a table correlating the features of various Posix-conforming systems.
7757 possibly terminated by an ellipsis `...' if C99 syntax is employed.
7810 other macro calls or shell code; that can cause syntax errors in the
8609 allow one to adjust the syntax of the language to adjust it to one's
8632 `--quotes', `--comments', `--words', and `--syntax'. Nevertheless,
8643 syntax is often not enough: if you happened to invoke macros in between,
8644 these macros are lost, as the current syntax is probably not the one
8742 Builtins: case.). With syntax highlighting editors, the presence of
8743 unbalanced `)' can interfere with editors that perform syntax
8951 It supports an extended syntax for the FILES:
9011 Warnings about `syntax' are enabled by default, and the environment
9016 autom4te --warnings=syntax,$WARNINGS,CATEGORY
9060 `--mode=OCTAL-MODE'
9062 Set the mode of the non-traces output to OCTAL-MODE; by default
9199 m4sugar/m4sugar.m4f --warnings syntax foo.m4
9206 m4sugar/m4sugar.m4f m4sugar/m4sh.m4f --mode 777 foo.m4
9230 use the traditional shell syntax to quote the ARGUMENTS.
9352 and supports extended regular expression syntax.
9357 supports extended regular expression syntax.
9533 `syntax'
9584 detail, and a syntax warning is issued if a diversion number is used
11014 syntax highlighting editors. The current implementation expands
11221 Therefore, the syntax for a valid EXPRESSION is rather limited:
11706 Report MESSAGE as a syntax warning. This macro is obsolescent;
11708 m4_warn([syntax], [MESSAGE])
11711 with syntax).
11847 `TESTA' even though it has already been expanded, but issues a syntax
11888 syntax warnings, whether the script is built with old or new Autoconf
12082 syntax-highlighting editors, from behaving improperly. For instance,
12363 Posix mode is buggy and causes `pdksh' to depart from Posix in at
12398 syntax error. The problem does not occur if a character follows the
12403 bash: -c: line 2: syntax error: unexpected end of file
12667 match the read/write mode that the file descriptor was opened with.
12975 `[!-aeiou]'. The older syntax `[^-aeiou]' is supported by some shells
13017 prints spurious quotes when in Posix mode:
13031 mode. In the example below, the correct behavior is to have five
13416 syntax error: `(' unexpected
13457 requires `eval' to avoid syntax errors. The following construct
13910 unless it is operating in Bourne shell compatibility mode and the
13933 running in Posix mode. Therefore, take care when exporting or
13935 Posix mode.
13981 ksh: syntax error at line 1: `}' unexpected
14077 Not all shells gracefully handle syntax errors within a sourced
14080 fails to react to the syntax error.
14082 $ echo 'fi' > syntax
14083 $ bash -c '. ./syntax; echo $?'
14084 ./syntax: line 1: syntax error near unexpected token `fi'
14085 ./syntax: line 1: `fi'
14087 $ ash -c '. ./syntax; echo $?'
14088 ./syntax: 1: Syntax error: "fi" unexpected
14089 $ zsh -c '. ./syntax; echo $?'
14090 ./syntax:1: parse error near `fi'
14145 Posix requires a syntax error if a brace list has no contents.
14151 bash: line 1: syntax error near unexpected token `}'
14180 error-->syntax error: `(' unexpected
14184 as when using a syntax-highlighting editor that searches for the
14293 outputs 2, but Bash and Zsh (in `sh' emulation mode) output 1.
14325 value=table_$key' to simulate a hash table when the key is known
14506 But keep in mind that Zsh, even in Bourne shell emulation mode,
14744 mode, asynchronous notification (`set -b') is enabled by default,
14745 and using `emulate sh' to switch to Posix mode does not clear this
14768 informing you about better syntax, but switching the script to use
14769 the suggested syntax in order to silence the warnings would render
14848 current user id compared to file owner and mode, as if by
15217 file unwritable, since it does not affect mode bits that
15218 correspond to bits in the file mode creation mask. Second, Posix
15220 implementation-specific option, not as a mode; Posix suggests
15651 temporary file name is to create a temporary directory with mode
16202 which fails with a syntax error, due to the Bash bug. To avoid this
16304 This syntax (`foo=bar make -e') is portable only when used outside
16387 such a setting it enters a special emulation mode where features like
16440 When NetBSD or FreeBSD `make' are run in parallel mode, they will
16472 The BSD `make' implementations, when run in parallel mode, will also
16485 mode, it implements the `@' and `-' "recipe modifiers" by dynamically
16542 parallel mode for targets being updated by Solaris `dmake' and NetBSD
16617 them even within quotes. Thus, the following might lead to a syntax
16815 undesirable. In fact, `make' is completely unaware of shell syntax
16832 sh: syntax error at line 1: `do' unexpected
16939 `$(HEADERS)' can be empty, because some shells diagnose a syntax error
17900 cross-compilation mode.
17906 enables cross-compilation mode.
17916 cross-compilation mode, use a command like this
20160 comment syntax for all the kinds of files that people call `AC_OUTPUT'
20187 the documentation for them. *Note Obsolete Macros::, for a table
20443 - the enabling of cross-compilation mode.
20457 they're different, `configure' enters cross compilation mode, so it
20490 `configure' could even enter cross-compilation mode only because the
20495 Now, `configure' enters cross-compilation mode if and only if
20505 mode. This is fragile. Moreover, by the time the compiler test is
20512 enters cross-compilation mode. The former interface, which consisted
20582 In addition to the change of syntax, the philosophy has changed too:
20722 mode" (*note testsuite Invocation::). The automatic generation of
21058 literals in the following table, then the test treats the output
21164 If the testsuite is run in verbose mode, with option `--verbose',
21165 EUnit is also run in verbose mode to output more details about
21197 In parallel mode, the standard input device of the testsuite
21205 Parallel mode requires the `mkfifo' command to work, and will be
21272 testsuite is run in parallel mode using `--jobs', then
21283 `always', test results will be colored. With `never', color mode
21388 AUTOTEST = $(AUTOM4TE) --language=autotest
21814 duplicate output and a syntax warning:
21933 levels, in M4 syntax or semantics, shell script issues, or due to bugs
21936 input contains syntax errors, this can make debugging rather painful.
21960 has invalid shell syntax. You can detect this case by running
22090 is table driven; it is meant to deal mainly with a discrete number of