diff options
| author | P. J. McDermott <pjm@nac.net> | 2012-10-13 12:51:59 (EDT) |
|---|---|---|
| committer | P. J. McDermott <pjm@nac.net> | 2012-10-13 13:18:56 (EDT) |
| commit | f1d89b5222cffe8ddb5de0952c8b13f5a6be3c53 (patch) | |
| tree | aa5f84e5e68c78d7074cebd1558bcf7128ea4043 /tests/ob_parse_dep.rc | |
| parent | 5ea0ae4037cb9d92981e60f1181a62af235cc40f (diff) | |
Don't rely on POSIX-conformant comment parsing.
POSIX.1-2008 specifies that comments in makefile syntax start with a "#"
and continue "until an **unescaped** <newline> is reached" (empahsis
added).
FreeBSD's pmake apparently ignores the backslash before the newline in
comments and prints a "Need an operator" error message while parsing a
generated src/Makefile:
$ make
Making executable files...
"Makefile", line 49: Need an operator
make: fatal errors encountered -- cannot continue
NetBSD's pmake on the other hand appears to be POSIX-conformant in this
regard.
See also:
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/make.html#tag_20_76_13_01
https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Backslash_002dNewline-Comments.html
Diffstat (limited to 'tests/ob_parse_dep.rc')
0 files changed, 0 insertions, 0 deletions