diff options
| author | Ron Yorston <rmy@pobox.com> | 2024-09-10 13:47:56 +0100 |
|---|---|---|
| committer | Ron Yorston <rmy@pobox.com> | 2024-09-10 13:47:56 +0100 |
| commit | 0b87e69888e52ce5ca797560124564efc794414c (patch) | |
| tree | a4ccfbad0223339188c757f0e2f28752146277aa /docs | |
| parent | b4d811aa232df8c7416a14f38a2396b028c35ac9 (diff) | |
| download | busybox-w32-0b87e69888e52ce5ca797560124564efc794414c.tar.gz busybox-w32-0b87e69888e52ce5ca797560124564efc794414c.tar.bz2 busybox-w32-0b87e69888e52ce5ca797560124564efc794414c.zip | |
make: handling of leading whitespace in makefiles
Try to match how different makes handle leading whitespace in
makefiles. (Tested with GNU, BSD, Schily and UNIX Version 7
make.)
- Commands in rules must start with a tab. It's the law.
- BSD make doesn't allow any whitespace at the start of an include
line. Enforce this restriction in POSIX mode: 'the word include
... appears at the beginning of a line'. As an extension allow
arbitrary tabs or spaces.
- All implementations allow a space as the first character of a
macro definition or rule. Permit this in all cases.
- Only GNU make allows a tab as the first character of a macro
definition, but POSIX 2024 seems to permit it too: 'string1 is
defined as all characters from the first non-<blank> character to
the last non-<blank> character, inclusive'. Allow this in POSIX
2024 mode and as an extension.
- No implementation allows a tab as the first character of a rule.
Disallow this in all cases.
Adds 32-64 bytes.
(pdpmake GitHub issue 63)
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions