dfbb6d0884
right/consistent. If you had something like: file file.c foo bar baz needs-flag and any one of foo, bar, or baz caused it to be brought into the compile, in the header you'd end up with: #define NFOO 1 #define NBAR 1 #define NBAZ 1 even if only one of them were selected. Other headers might have had a different (inconsistent) set of definitions, depending on whether any of their components were included, and any files necessary for the unspecified options would not actually be present in the Makefile files list. The correct behaviour for the example above if only 'foo' is selected by the config file is: #define NFOO 1 #define NBAR 0 #define NBAZ 0 which is what config now does. This bug has been present for a while. (I don't know for sure that it was present in 4.4-Lite2, but from looking at the Lite2 config sources, it appears to be there.) |
||
|---|---|---|
| bin | ||
| distrib | ||
| etc | ||
| games | ||
| gnu | ||
| include | ||
| lib | ||
| libexec | ||
| regress | ||
| sbin | ||
| share | ||
| sys | ||
| usr.bin | ||
| usr.sbin | ||
| Makefile | ||