Appendix B: Errors Generated by Make 175
‘missing target pattern. Stop.’
‘multiple target patterns. Stop.’
‘target pattern contains no ‘%’. Stop.’
‘mixed implicit and static pattern rules. Stop.’
These are generated for malformed static pattern rules. The first means there’s
no pattern in the target section of the rule; the second means there are multiple
patterns in the target section; the third means the target doesn’t contain a
pattern character (%); and the fourth means that all three parts of the static
pattern rule contain pattern characters (%)–only the first two parts should. If
you see these errors and you aren’t trying to create a static pattern rule, check
the value of any variables in your target and prerequisite lists to be sure they do
not contain colons. See Section 4.11.1 [Syntax of Static Pattern Rules], page 36.
‘warning: -jN forced in submake: disabling jobserver mode.’
This warning and the next are generated if make detects error conditions re-
lated to parallel processing on systems where sub-makes can communicate (see
Section 5.7.3 [Communicating Options to a Sub-make], page 54). This warning
is generated if a recursive invocation of a make process is forced to have ‘-jN’
in its argument list (where N is greater than one). This could happen, for
example, if you set the MAKE environment variable to ‘make -j2’. In this case,
the sub-make doesn’t communicate with other make processes and will simply
pretend it has two jobs of its own.
‘warning: jobserver unavailable: using -j1. Add ‘+’ to parent make rule.’
In order for make processes to communicate, the parent will pass information to
the child. Since this could result in problems if the child process isn’t actually
a make, the parent will only do this if it thinks the child is a make. The parent
uses the normal algorithms to determine this (see Section 5.7.1 [How the MAKE
Variable Works], page 51). If the makefile is constructed such that the parent
doesn’t know the child is a make process, then the child will receive only part
of the information necessary. In this case, the child will generate this warning
message and proceed with its build in a sequential manner.
Comentários a estes Manuais