make programs in various other systems support a few features
that are not implemented in GNU
make. The POSIX.2 standard
(IEEE Standard 1003.2-1992) which specifies
make does not
require any of these features.
A target of the form ‘
file((entry))’ stands for a member
of archive file
file. The member is chosen, not by name, but by
being an object file which defines the linker symbol
This feature was not put into GNU
make because of the
non-modularity of putting knowledge into
make of the internal
format of archive file symbol tables.
See Updating Archive Symbol Directories.
Suffixes (used in suffix rules) that end with the character ‘
have a special meaning to System V
they refer to the SCCS file that corresponds
to the file one would get without the ‘
~’. For example, the
suffix rule ‘
.c~.o’ would make the file
the SCCS file
s.n.c. For complete coverage, a whole
series of such suffix rules is required.
See Old-Fashioned Suffix Rules.
make, this entire series of cases is handled by two
pattern rules for extraction from SCCS, in combination with the
general feature of rule chaining.
See Chains of Implicit Rules.
make, files found by
VPATHsearch (see Searching Directories for Prerequisites) have their names changed inside recipes. We feel it is much cleaner to always use automatic variables and thus make this feature unnecessary.
makes, the automatic variable
$*appearing in the prerequisites of a rule has the amazingly strange “feature” of expanding to the full name of the target of that rule. We cannot imagine what went on in the minds of Unix
makedevelopers to do this; it is utterly inconsistent with the normal definition of
In some Unix
makes, implicit rule search (see Using Implicit Rules) is apparently done for all
targets, not just those without recipes. This means you can
foo.o: cc -c foo.c
make will intuit that
foo.o depends on
We feel that such usage is broken. The prerequisite properties of
make are well-defined (for GNU
make, at least),
and doing such a thing simply does not fit the model.
makedoes not include any built-in implicit rules for compiling or preprocessing EFL programs. If we hear of anyone who is using EFL, we will gladly add them.
It appears that in SVR4
make, a suffix rule can be specified
with no recipe, and it is treated as if it had an empty recipe
(see Empty Recipes). For example:
will override the built-in
.c.a suffix rule.
We feel that it is cleaner for a rule without a recipe to always simply
add to the prerequisite list for the target. The above example can be
easily rewritten to get the desired behavior in GNU
makeinvoke the shell with the ‘
-e’ flag, except under ‘
-k’ (see Testing the Compilation of a Program). The ‘
-e’ flag tells the shell to exit as soon as any program it runs returns a nonzero status. We feel it is cleaner to write each line of the recipe to stand on its own and not require this special treatment.