1 GNU make NEWS -*-indented-text-*-
2 History of user-visible changes.
5 See the end of this file for copyrights and conditions.
7 All changes mentioned here are more fully described in the GNU make
8 manual, which is contained in this distribution as the file doc/make.texi.
9 See the README file and the GNU make manual for instructions for
14 A complete list of bugs fixed in this version is available here:
16 http://sv.gnu.org/bugs/index.php?group=make&report_id=111&fix_release_id=104&set=custom
18 * Compiling GNU make now requires a conforming ISO C 1989 compiler and
19 standard runtime library.
21 * WARNING: Backward-incompatibility!
22 The POSIX standard for make was changed in the 2008 version in a
23 fundamentally incompatible way: make is required to invoke the shell as if
24 the '-e' flag were provided. Because this would break many makefiles that
25 have been written to conform to the original text of the standard, the
26 default behavior of GNU make remains to invoke the shell with simply '-c'.
27 However, any makefile specifying the .POSIX special target will follow the
28 new POSIX standard and pass '-e' to the shell. See also .SHELLFLAGS
31 * WARNING: Backward-incompatibility!
32 The '$?' variable now contains all prerequisites that caused the target to
33 be considered out of date, even if they do not exist (previously only
34 existing targets were provided in $?).
36 * WARNING: Backward-incompatibility!
37 Wildcards were not documented as returning sorted values, but the results
38 have been sorted up until this release.. If your makefiles require sorted
39 results from wildcard expansions, use the $(sort ...) function to request
42 * WARNING: Backward-incompatibility!
43 In previous versions of make it was acceptable to list one or more explicit
44 targets followed by one or more pattern targets in the same rule and it
45 worked "as expected". However, this was not documented as acceptable and if
46 you listed any explicit targets AFTER the pattern targets, the entire rule
47 would be mis-parsed. This release removes this ability completely: make
48 will generate an error message if you mix explicit and pattern targets in
51 * WARNING: Backward-incompatibility!
52 As a result of parser enhancements, three backward-compatibility issues
53 exist: first, a prerequisite containing an "=" cannot be escaped with a
54 backslash any longer. You must create a variable containing an "=" and
55 use that variable in the prerequisite. Second, variable names can no
56 longer contain whitespace, unless you put the whitespace in a variable and
57 use the variable. Third, in previous versions of make it was sometimes
58 not flagged as an error for explicit and pattern targets to appear in the
59 same rule. Now this is always reported as an error.
61 * WARNING: Backward-incompatibility!
62 The pattern-specific variables and pattern rules are now applied in the
63 shortest stem first order instead of the definition order (variables
64 and rules with the same stem length are still applied in the definition
65 order). This produces the usually-desired behavior where more specific
66 patterns are preferred. To detect this feature search for 'shortest-stem'
67 in the .FEATURES special variable.
69 * WARNING: Backward-incompatibility!
70 The library search behavior has changed to be compatible with the standard
71 linker behavior. Prior to this version for prerequisites specified using
72 the -lfoo syntax make first searched for libfoo.so in the current
73 directory, vpath directories, and system directories. If that didn't yield
74 a match, make then searched for libfoo.a in these directories. Starting
75 with this version make searches first for libfoo.so and then for libfoo.a
76 in each of these directories in order.
78 * New command line option: --eval=STRING causes STRING to be evaluated as
79 makefile syntax (akin to using the $(eval ...) function). The evaluation
80 is performed after all default rules and variables are defined, but before
81 any makefiles are read.
83 * New special variable: .RECIPEPREFIX allows you to reset the recipe
84 introduction character from the default (TAB) to something else. The
85 first character of this variable value is the new recipe introduction
86 character. If the variable is set to the empty string, TAB is used again.
87 It can be set and reset at will; recipes will use the value active when
88 they were first parsed. To detect this feature check the value of
91 * New special variable: .SHELLFLAGS allows you to change the options passed
92 to the shell when it invokes recipes. By default the value will be "-c"
93 (or "-ec" if .POSIX is set).
95 * New special target: .ONESHELL instructs make to invoke a single instance
96 of the shell and provide it with the entire recipe, regardless of how many
97 lines it contains. As a special feature to allow more straightforward
98 conversion of makefiles to use .ONESHELL, any recipe line control
99 characters ('@', '+', or '-') will be removed from the second and
100 subsequent recipe lines. This happens _only_ if the SHELL value is deemed
101 to be a standard POSIX-style shell. If not, then no interior line control
102 characters are removed (as they may be part of the scripting language used
103 with the alternate SHELL).
105 * New variable modifier 'private': prefixing a variable assignment with the
106 modifier 'private' suppresses inheritance of that variable by
107 prerequisites. This is most useful for target- and pattern-specific
110 * New make directive: 'undefine' allows you to undefine a variable so that
111 it appears as if it was never set. Both $(flavor) and $(origin) functions
112 will return 'undefined' for such a variable. To detect this feature search
113 for 'undefine' in the .FEATURES special variable.
115 * The parser for variable assignments has been enhanced to allow multiple
116 modifiers ('export', 'override', 'private') on the same line as variables,
117 including define/endef variables, and in any order. Also, it is possible
118 to create variables and targets named as these modifiers.
120 * The 'define' make directive now allows a variable assignment operator
121 after the variable name, to allow for simple, conditional, or appending
122 multi-line variable assignment.
127 * GNU make is ported to OS/2.
129 * GNU make is ported to MinGW. The MinGW build is only supported by
130 the build_w32.bat batch file; see the file README.W32 for more
133 * WARNING: Future backward-incompatibility!
134 Up to and including this release, the '$?' variable does not contain
135 any prerequisite that does not exist, even though that prerequisite
136 might have caused the target to rebuild. Starting with the _next_
137 release of GNU make, '$?' will contain all prerequisites that caused
138 the target to be considered out of date. See this Savannah bug:
139 http://savannah.gnu.org/bugs/index.php?func=detailitem&item_id=16051
141 * WARNING: Backward-incompatibility!
142 GNU make now implements a generic "second expansion" feature on the
143 prerequisites of both explicit and implicit (pattern) rules. In order
144 to enable this feature, the special target '.SECONDEXPANSION' must be
145 defined before the first target which takes advantage of it. If this
146 feature is enabled then after all rules have been parsed the
147 prerequisites are expanded again, this time with all the automatic
148 variables in scope. This means that in addition to using standard
149 SysV $$@ in prerequisites lists, you can also use complex functions
150 such as $$(notdir $$@) etc. This behavior applies to implicit rules,
151 as well, where the second expansion occurs when the rule is matched.
152 However, this means that when '.SECONDEXPANSION' is enabled you must
153 double-quote any "$" in your filenames; instead of "foo: boo$$bar" you
154 now must write "foo: foo$$$$bar". Note that the SysV $$@ etc. feature,
155 which used to be available by default, is now ONLY available when the
156 .SECONDEXPANSION target is defined. If your makefiles take advantage
157 of this SysV feature you will need to update them.
159 * WARNING: Backward-incompatibility!
160 In order to comply with POSIX, the way in which GNU make processes
161 backslash-newline sequences in recipes has changed. If your makefiles
162 use backslash-newline sequences inside of single-quoted strings in
163 recipes you will be impacted by this change. See the GNU make manual
164 subsection "Splitting Recipe Lines" (node "Splitting Lines"), in
165 section "Recipe Syntax", chapter "Writing Recipe in Rules", for
168 * WARNING: Backward-incompatibility!
169 Some previous versions of GNU make had a bug where "#" in a function
170 invocation such as $(shell ...) was treated as a make comment. A
171 workaround was to escape these with backslashes. This bug has been
172 fixed: if your makefile uses "\#" in a function invocation the
173 backslash is now preserved, so you'll need to remove it.
175 * New command line option: -L (--check-symlink-times). On systems that
176 support symbolic links, if this option is given then GNU make will
177 use the most recent modification time of any symbolic links that are
178 used to resolve target files. The default behavior remains as it
179 always has: use the modification time of the actual target file only.
181 * The "else" conditional line can now be followed by any other valid
182 conditional on the same line: this does not increase the depth of the
183 conditional nesting, so only one "endif" is required to close the
186 * All pattern-specific variables that match a given target are now used
187 (previously only the first match was used).
189 * Target-specific variables can be marked as exportable using the
192 * In a recursive $(call ...) context, any extra arguments from the outer
193 call are now masked in the context of the inner call.
195 * Implemented a solution for the "thundering herd" problem with "-j -l".
196 This version of GNU make uses an algorithm suggested by Thomas Riedl
197 <thomas.riedl@siemens.com> to track the number of jobs started in the
198 last second and artificially adjust GNU make's view of the system's
199 load average accordingly.
201 * New special variables available in this release:
202 - .INCLUDE_DIRS: Expands to a list of directories that make searches
203 for included makefiles.
204 - .FEATURES: Contains a list of special features available in this
206 - .DEFAULT_GOAL: Set the name of the default goal make will
207 use if no goals are provided on the command line.
208 - MAKE_RESTARTS: If set, then this is the number of times this
209 instance of make has been restarted (see "How Makefiles Are Remade"
211 - New automatic variable: $| (added in 3.80, actually): contains all
212 the order-only prerequisites defined for the target.
214 * New functions available in this release:
215 - $(lastword ...) returns the last word in the list. This gives
216 identical results as $(word $(words ...) ...), but is much faster.
217 - $(abspath ...) returns the absolute path (all "." and ".."
218 directories resolved, and any duplicate "/" characters removed) for
220 - $(realpath ...) returns the canonical pathname for each path
221 provided. The canonical pathname is the absolute pathname, with
222 all symbolic links resolved as well.
223 - $(info ...) prints its arguments to stdout. No makefile name or
224 line number info, etc. is printed.
225 - $(flavor ...) returns the flavor of a variable.
226 - $(or ...) provides a short-circuiting OR conditional: each argument
227 is expanded. The first true (non-empty) argument is returned; no
228 further arguments are expanded. Expands to empty if there are no
230 - $(and ...) provides a short-circuiting AND conditional: each
231 argument is expanded. The first false (empty) argument is
232 returned; no further arguments are expanded. Expands to the last
233 argument if all arguments are true.
235 * Changes made for POSIX compatibility:
236 - Only touch targets (under -t) if they have a recipe.
237 - Setting the SHELL make variable does NOT change the value of the
238 SHELL environment variable given to programs invoked by make. As
239 an enhancement to POSIX, if you export the make variable SHELL then
240 it will be set in the environment, just as before.
242 * On MS Windows systems, explicitly setting SHELL to a pathname ending
243 in "cmd" or "cmd.exe" (case-insensitive) will force GNU make to use
244 the DOS command interpreter in batch mode even if a UNIX-like shell
245 could be found on the system.
247 * On VMS there is now support for case-sensitive filesystems such as ODS5.
248 See the readme.vms file for information.
250 * Parallel builds (-jN) no longer require a working Bourne shell on
251 Windows platforms. They work even with the stock Windows shells, such
252 as cmd.exe and command.com.
254 * Updated to autoconf 2.59, automake 1.9.5, and gettext 0.14.1. Users
255 should not be impacted.
257 * New translations for Swedish, Chinese (simplified), Ukrainian,
258 Belarusian, Finnish, Kinyarwandan, and Irish. Many updated
261 A complete list of bugs fixed in this version is available here:
263 http://savannah.gnu.org/bugs/index.php?group=make&report_id=111&fix_release_id=103
268 * A new feature exists: order-only prerequisites. These prerequisites
269 affect the order in which targets are built, but they do not impact
270 the rebuild/no-rebuild decision of their dependents. That is to say,
271 they allow you to require target B be built before target A, without
272 requiring that target A will always be rebuilt if target B is updated.
273 Patch for this feature provided by Greg McGary <greg@mcgary.org>.
275 * For compatibility with SysV make, GNU make now supports the peculiar
276 syntax $$@, $$(@D), and $$(@F) in the prerequisites list of a rule.
277 This syntax is only valid within explicit and static pattern rules: it
278 cannot be used in implicit (suffix or pattern) rules. Edouard G. Parmelan
279 <egp@free.fr> provided a patch implementing this feature; however, I
280 decided to implement it in a different way.
282 * The argument to the "ifdef" conditional is now expanded before it's
283 tested, so it can be a constructed variable name.
285 Similarly, the arguments to "export" (when not used in a variable
286 definition context) and "unexport" are also now expanded.
288 * A new function is defined: $(value ...). The argument to this
289 function is the _name_ of a variable. The result of the function is
290 the value of the variable, without having been expanded.
292 * A new function is defined: $(eval ...). The arguments to this
293 function should expand to makefile commands, which will then be
294 evaluated as if they had appeared in the makefile. In combination
295 with define/endef multiline variable definitions this is an extremely
296 powerful capability. The $(value ...) function is also sometimes
299 * A new built-in variable is defined, $(MAKEFILE_LIST). It contains a
300 list of each makefile GNU make has read, or started to read, in the
301 order in which they were encountered. So, the last filename in the
302 list when a makefile is just being read (before any includes) is the
303 name of the current makefile.
305 * A new built-in variable is defined: $(.VARIABLES). When it is
306 expanded it returns a complete list of variable names defined by all
307 makefiles at that moment.
309 * A new command line option is defined, -B or --always-make. If
310 specified GNU make will consider all targets out-of-date even if they
311 would otherwise not be.
313 * The arguments to $(call ...) functions were being stored in $1, $2,
314 etc. as recursive variables, even though they are fully expanded
315 before assignment. This means that escaped dollar signs ($$ etc.)
316 were not behaving properly. Now the arguments are stored as simple
317 variables. This may mean that if you added extra escaping to your
318 $(call ...) function arguments you will need to undo it now.
320 * The variable invoked by $(call ...) can now be recursive: unlike other
321 variables it can reference itself and this will not produce an error
322 when it is used as the first argument to $(call ...) (but only then).
324 * New pseudo-target .LOW_RESOLUTION_TIME, superseding the configure
325 option --disable-nsec-timestamps. You might need this if your build
326 process depends on tools like "cp -p" preserving time stamps, since
327 "cp -p" (right now) doesn't preserve the subsecond portion of a time
330 * Updated translations for French, Galician, German, Japanese, Korean,
331 and Russian. New translations for Croatian, Danish, Hebrew, and
334 * Updated internationalization support to Gettext 0.11.5.
335 GNU make now uses Gettext's "external" feature, and does not include
336 any internationalization code itself. Configure will search your
337 system for an existing implementation of GNU Gettext (only GNU Gettext
338 is acceptable) and use it if it exists. If not, NLS will be disabled.
339 See ABOUT-NLS for more information.
341 * Updated to autoconf 2.54 and automake 1.7. Users should not be impacted.
343 A complete list of bugs fixed in this version is available here:
345 http://savannah.gnu.org/bugs/index.php?group=make&report_id=111&fix_release_id=102
350 * .SECONDARY with no prerequisites now prevents any target from being
351 removed because make thinks it's an intermediate file, not just those
352 listed in the makefile.
354 * New configure option --disable-nsec-timestamps, but this was
355 superseded in later versions by the .LOW_RESOLUTION_TIME pseudo-target.
359 * GNU make optionally supports internationalization and locales via the
360 GNU gettext (or local gettext if suitable) package. See the ABOUT-NLS
361 file for more information on configuring GNU make for NLS.
363 * Previously, GNU make quoted variables such as MAKEFLAGS and
364 MAKEOVERRIDES for proper parsing by the shell. This allowed them to
365 be used within make build scripts. However, using them there is not
366 proper behavior: they are meant to be passed to subshells via the
367 environment. Unfortunately the values were not quoted properly to be
368 passed through the environment. This meant that make didn't properly
369 pass some types of command line values to submakes.
371 With this version we change that behavior: now these variables are
372 quoted properly for passing through the environment, which is the
373 correct way to do it. If you previously used these variables
374 explicitly within a make rule you may need to re-examine your use for
375 correctness given this change.
377 * A new pseudo-target .NOTPARALLEL is available. If defined, the
378 current makefile is run serially regardless of the value of -j.
379 However, submakes are still eligible for parallel execution.
381 * The --debug option has changed: it now allows optional flags
382 controlling the amount and type of debugging output. By default only
383 a minimal amount information is generated, displaying the names of
384 "normal" targets (not makefiles) that were deemed out of date and in
385 need of being rebuilt.
387 Note that the -d option behaves as before: it takes no arguments and
388 all debugging information is generated.
390 * The `-p' (print database) output now includes filename and linenumber
391 information for variable definitions, to aid debugging.
393 * The wordlist function no longer reverses its arguments if the "start"
394 value is greater than the "end" value. If that's true, nothing is
397 * Hartmut Becker provided many updates for the VMS port of GNU make.
398 See the readme.vms file for more details.
402 * Two new functions, $(error ...) and $(warning ...) are available. The
403 former will cause make to fail and exit immediately upon expansion of
404 the function, with the text provided as the error message. The latter
405 causes the text provided to be printed as a warning message, but make
408 * A new function $(call ...) is available. This allows users to create
409 their own parameterized macros and invoke them later. Original
410 implementation of this function was provided by Han-Wen Nienhuys
413 * A new function $(if ...) is available. It provides if-then-else
414 capabilities in a builtin function. Original implementation of this
415 function was provided by Han-Wen Nienhuys <hanwen@cs.uu.nl>.
417 * Make defines a new variable, .LIBPATTERNS. This variable controls how
418 library dependency expansion (dependencies like ``-lfoo'') is performed.
420 * Make accepts CRLF sequences as well as traditional LF, for
421 compatibility with makefiles created on other operating systems.
423 * Make accepts a new option: -R, or --no-builtin-variables. This option
424 disables the definition of the rule-specific builtin variables (CC,
425 LD, AR, etc.). Specifying this option forces -r (--no-builtin-rules)
428 * A "job server" feature, suggested by Howard Chu <hyc@highlandsun.com>.
430 On systems that support POSIX pipe(2) semantics, GNU make can now pass
431 -jN options to submakes rather than forcing them all to use -j1. The
432 top make and all its sub-make processes use a pipe to communicate with
433 each other to ensure that no more than N jobs are started across all
434 makes. To get the old behavior of -j back, you can configure make
435 with the --disable-job-server option.
437 * The confusing term "dependency" has been replaced by the more accurate
438 and standard term "prerequisite", both in the manual and in all GNU make
441 * GNU make supports the "big archive" library format introduced in AIX 4.3.
443 * GNU make supports large files on AIX, HP-UX, and IRIX. These changes
444 were provided by Paul Eggert <eggert@twinsun.com>. (Large file
445 support for Solaris and Linux was introduced in 3.77, but the
446 configuration had issues: these have also been resolved).
448 * The Windows 95/98/NT (W32) version of GNU make now has native support
449 for the Cygnus Cygwin release B20.1 shell (bash).
451 * The GNU make regression test suite, long available separately "under
452 the table", has been integrated into the release. You can invoke it
453 by running "make check" in the distribution. Note that it requires
454 Perl (either Perl 4 or Perl 5) to run.
458 * Implement BSD make's "?=" variable assignment operator. The variable
459 is assigned the specified value only if that variable is not already
462 * Make defines a new variable, "CURDIR", to contain the current working
463 directory (after the -C option, if any, has been processed).
464 Modifying this variable has no effect on the operation of make.
466 * Make defines a new default RCS rule, for new-style master file
467 storage: ``% :: RCS/%'' (note no ``,v'' suffix).
469 Make defines new default rules for DOS-style C++ file naming
470 conventions, with ``.cpp'' suffixes. All the same rules as for
471 ``.cc'' and ``.C'' suffixes are provided, along with LINK.cpp and
472 COMPILE.cpp macros (which default to the same value as LINK.cc and
473 COMPILE.cc). Note CPPFLAGS is still C preprocessor flags! You should
474 use CXXFLAGS to change C++ compiler flags.
476 * A new feature, "target-specific variable values", has been added.
477 This is a large change so please see the appropriate sections of the
478 manual for full details. Briefly, syntax like this:
480 TARGET: VARIABLE = VALUE
482 defines VARIABLE as VALUE within the context of TARGET. This is
483 similar to SunOS make's "TARGET := VARIABLE = VALUE" feature. Note
484 that the assignment may be of any type, not just recursive, and that
485 the override keyword is available.
487 COMPATIBILITY: This new syntax means that if you have any rules where
488 the first or second dependency has an equal sign (=) in its name,
489 you'll have to escape them with a backslash: "foo : bar\=baz".
490 Further, if you have any dependencies which already contain "\=",
491 you'll have to escape both of them: "foo : bar\\\=baz".
493 * A new appendix listing the most common error and warning messages
494 generated by GNU make, with some explanation, has been added to the
495 GNU make User's Manual.
497 * Updates to the GNU make Customs library support (see README.customs).
499 * Updates to the Windows 95/NT port from Rob Tulloh (see README.W32),
500 and to the DOS port from Eli Zaretski (see README.DOS).
504 * Small (but serious) bug fix. Quick rollout to get into the GNU source CD.
508 * GNU make now uses automake to control Makefile.in generation. This
509 should make it more consistent with the GNU standards.
511 * VPATH functionality has been changed to incorporate the VPATH+ patch,
512 previously maintained by Paul Smith <psmith@baynetworks.com>. See the
515 * Make defines a new variable, `MAKECMDGOALS', to contain the goals that
516 were specified on the command line, if any. Modifying this variable
517 has no effect on the operation of make.
519 * A new function, `$(wordlist S,E,TEXT)', is available: it returns a
520 list of words from number S to number E (inclusive) of TEXT.
522 * Instead of an error, detection of future modification times gives a
523 warning and continues. The warning is repeated just before GNU make
524 exits, so it is less likely to be lost.
526 * Fix the $(basename) and $(suffix) functions so they only operate on
527 the last filename, not the entire string:
529 Command Old Result New Result
530 ------- ---------- ----------
532 $(basename a.b/c) a a.b/c
534 $(suffix a.b/c) b/c <empty>
536 * The $(strip) function now removes newlines as well as TABs and spaces.
538 * The $(shell) function now changes CRLF (\r\n) pairs to a space as well
541 * Updates to the Windows 95/NT port from Rob Tulloh (see README.W32).
543 * Eli Zaretskii has updated the port to 32-bit protected mode on MSDOS
544 and MS-Windows, building with the DJGPP v2 port of GNU C/C++ compiler
545 and utilities. See README.DOS for details, and direct all questions
546 concerning this port to Eli Zaretskii <eliz@is.elta.co.il> or DJ
547 Delorie <dj@delorie.com>.
549 * John W. Eaton has updated the VMS port to support libraries and VPATH.
553 * The directory messages printed by `-w' and implicitly in sub-makes,
554 are now omitted if Make runs no commands and has no other messages to print.
556 * Make now detects files that for whatever reason have modification times
557 in the future and gives an error. Files with such impossible timestamps
558 can result from unsynchronized clocks, or archived distributions
559 containing bogus timestamps; they confuse Make's dependency engine
562 * The new directive `sinclude' is now recognized as another name for
563 `-include', for compatibility with some other Makes.
565 * Aaron Digulla has contributed a port to AmigaDOS. See README.Amiga for
566 details, and direct all Amiga-related questions to <digulla@fh-konstanz.de>.
568 * Rob Tulloh of Tivoli Systems has contributed a port to Windows NT or 95.
569 See README.W32 for details, and direct all Windows-related questions to
570 <rob_tulloh@tivoli.com>.
574 * Converted to use Autoconf version 2, so `configure' has some new options.
575 See INSTALL for details.
577 * You can now send a SIGUSR1 signal to Make to toggle printing of debugging
578 output enabled by -d, at any time during the run.
582 * DJ Delorie has ported Make to MS-DOS using the GO32 extender.
583 He is maintaining the DOS port, not the GNU Make maintainer;
584 please direct bugs and questions for DOS to <djgpp@sun.soe.clarkson.edu>.
585 MS-DOS binaries are available for FTP from ftp.simtel.net in
586 /pub/simtelnet/gnu/djgpp/.
588 * The `MAKEFLAGS' variable (in the environment or in a makefile) can now
589 contain variable definitions itself; these are treated just like
590 command line variable definitions. Make will automatically insert any
591 variable definitions from the environment value of `MAKEFLAGS' or from
592 the command line, into the `MAKEFLAGS' value exported to children. The
593 `MAKEOVERRIDES' variable previously included in the value of `$(MAKE)'
594 for sub-makes is now included in `MAKEFLAGS' instead. As before, you can
595 reset `MAKEOVERRIDES' in your makefile to avoid putting all the variables
596 in the environment when its size is limited.
598 * If `.DELETE_ON_ERROR' appears as a target, Make will delete the target of
599 a rule if it has changed when its recipe exits with a nonzero status,
600 just as when the recipe gets a signal.
602 * The automatic variable `$+' is new. It lists all the dependencies like
603 `$^', but preserves duplicates listed in the makefile. This is useful
604 for linking rules, where library files sometimes need to be listed twice
607 * You can now specify the `.IGNORE' and `.SILENT' special targets with
608 dependencies to limit their effects to those files. If a file appears as
609 a dependency of `.IGNORE', then errors will be ignored while running the
610 recipe to update that file. Likewise if a file appears as a dependency
611 of `.SILENT', then the recipe to update that file will not be printed
612 before it is run. (This change was made to conform to POSIX.2.)
616 * The automatic variables `$(@D)', `$(%D)', `$(*D)', `$(<D)', `$(?D)', and
617 `$(^D)' now omit the trailing slash from the directory name. (This change
618 was made to comply with POSIX.2.)
620 * The source distribution now includes the Info files for the Make manual.
621 There is no longer a separate distribution containing Info and DVI files.
623 * You can now set the variables `binprefix' and/or `manprefix' in
624 Makefile.in (or on the command line when installing) to install GNU make
625 under a name other than `make' (i.e., ``make binprefix=g install''
626 installs GNU make as `gmake').
628 * The built-in Texinfo rules use the new variables `TEXI2DVI_FLAGS' for
629 flags to the `texi2dvi' script, and `MAKEINFO_FLAGS' for flags to the
632 * The exit status of Make when it runs into errors is now 2 instead of 1.
633 The exit status is 1 only when using -q and some target is not up to date.
634 (This change was made to comply with POSIX.2.)
638 * It is no longer a fatal error to have a NUL character in a makefile.
639 You should never put a NUL in a makefile because it can have strange
640 results, but otherwise empty lines full of NULs (such as produced by
641 the `xmkmf' program) will always work fine.
643 * The error messages for nonexistent included makefiles now refer to the
644 makefile name and line number where the `include' appeared, so Emacs's
645 C-x ` command takes you there (in case it's a typo you need to fix).
649 * Implicit rule search for archive member references is now done in the
650 opposite order from previous versions: the whole target name `LIB(MEM)'
651 first, and just the member name and parentheses `(MEM)' second.
653 * Make now gives an error for an unterminated variable or function reference.
654 For example, `$(foo' with no matching `)' or `${bar' with no matching `}'.
656 * The new default variable `MAKE_VERSION' gives the version number of
657 Make, and a string describing the remote job support compiled in (if any).
658 Thus the value (in this release) is something like `3.69' or `3.69-Customs'.
660 * Commands in an invocation of the `shell' function are no longer run
661 with a modified environment like recipes are. As in versions before
662 3.68, they now run with the environment that `make' started with. We
663 have reversed the change made in version 3.68 because it turned out to
664 cause a paradoxical situation in cases like:
666 export variable = $(shell echo value)
668 When Make attempted to put this variable in the environment for a
669 recipe, it would try expand the value by running the shell command
670 `echo value'. In version 3.68, because it constructed an environment
671 for that shell command in the same way, Make would begin to go into an
672 infinite loop and then get a fatal error when it detected the loop.
674 * The recipe given for `.DEFAULT' is now used for phony targets with no
679 * You can list several archive member names inside parenthesis:
680 `lib(mem1 mem2 mem3)' is equivalent to `lib(mem1) lib(mem2) lib(mem3)'.
682 * You can use wildcards inside archive member references. For example,
683 `lib(*.o)' expands to all existing members of `lib' whose names end in
684 `.o' (e.g. `lib(a.o) lib(b.o)'); `*.a(*.o)' expands to all such members
685 of all existing files whose names end in `.a' (e.g. `foo.a(a.o)
686 foo.a(b.o) bar.a(c.o) bar.a(d.o)'.
688 * A suffix rule `.X.a' now produces two pattern rules:
689 (%.o): %.X # Previous versions produced only this.
690 %.a: %.X # Now produces this as well, just like other suffixes.
692 * The new flag `--warn-undefined-variables' says to issue a warning message
693 whenever Make expands a reference to an undefined variable.
695 * The new `-include' directive is just like `include' except that there is
696 no error (not even a warning) for a nonexistent makefile.
698 * Commands in an invocation of the `shell' function are now run with a
699 modified environment like recipes are, so you can use `export' et al
700 to set up variables for them. They used to run with the environment
701 that `make' started with.
705 * `make --version' (or `make -v') now exits immediately after printing
710 * Make now supports long-named members in `ar' archive files.
714 * Make now supports the `+=' syntax for a variable definition which appends
715 to the variable's previous value. See the section `Appending More Text
716 to Variables' in the manual for full details.
718 * The new option `--no-print-directory' inhibits the `-w' or
719 `--print-directory' feature. Make turns on `--print-directory'
720 automatically if you use `-C' or `--directory', and in sub-makes; some
721 users have found this behavior undesirable.
723 * The built-in implicit rules now support the alternative extension
724 `.txinfo' for Texinfo files, just like `.texinfo' and `.texi'.
728 * Make now uses a standard GNU `configure' script. See the new file
729 INSTALL for the new (and much simpler) installation procedure.
731 * There is now a shell script to build Make the first time, if you have no
732 other `make' program. `build.sh' is created by `configure'; see README.
734 * GNU Make now completely conforms to the POSIX.2 specification for `make'.
736 * Elements of the `$^' and `$?' automatic variables that are archive
737 member references now list only the member name, as in Unix and POSIX.2.
739 * You should no longer ever need to specify the `-w' switch, which prints
740 the current directory before and after Make runs. The `-C' switch to
741 change directory, and recursive use of Make, now set `-w' automatically.
743 * Multiple double-colon rules for the same target will no longer have their
744 recipes run simultaneously under -j, as this could result in the two
745 recipes trying to change the file at the same time and interfering with
748 * The `SHELL' variable is now never taken from the environment.
749 Each makefile that wants a shell other than the default (/bin/sh) must
750 set SHELL itself. SHELL is always exported to child processes.
751 This change was made for compatibility with POSIX.2.
753 * Make now accepts long options. There is now an informative usage message
754 that tells you what all the options are and what they do. Try `make --help'.
756 * There are two new directives: `export' and `unexport'. All variables are
757 no longer automatically put into the environments of the recipe lines that
758 Make runs. Instead, only variables specified on the command line or in
759 the environment are exported by default. To export others, use:
761 or you can define variables with:
762 export VARIABLE = VALUE
764 export VARIABLE := VALUE
768 .EXPORT_ALL_VARIABLES:
769 to get the old behavior. See the node `Variables/Recursion' in the manual
770 for a full description.
772 * The recipe from the `.DEFAULT' special target is only applied to
773 targets which have no rules at all, not all targets with no recipe.
774 This change was made for compatibility with Unix make.
776 * All fatal error messages now contain `***', so they are easy to find in
779 * Dependency file names like `-lNAME' are now replaced with the actual file
780 name found, as with files found by normal directory search (VPATH).
781 The library file `libNAME.a' may now be found in the current directory,
782 which is checked before VPATH; the standard set of directories (/lib,
783 /usr/lib, /usr/local/lib) is now checked last.
784 See the node `Libraries/Search' in the manual for full details.
786 * A single `include' directive can now specify more than one makefile to
789 You can also use shell file name patterns in an `include' directive:
792 * The default directories to search for included makefiles, and for
793 libraries specified with `-lNAME', are now set by configuration.
795 * You can now use blanks as well as colons to separate the directories in a
796 search path for the `vpath' directive or the `VPATH' variable.
798 * You can now use variables and functions in the left hand side of a
799 variable assignment, as in "$(foo)bar = value".
801 * The `MAKE' variable is always defined as `$(MAKE_COMMAND) $(MAKEOVERRIDES)'.
802 The `MAKE_COMMAND' variable is now defined to the name with which make
805 * The built-in rules for C++ compilation now use the variables `$(CXX)' and
806 `$(CXXFLAGS)' instead of `$(C++)' and `$(C++FLAGS)'. The old names had
807 problems with shells that cannot have `+' in environment variable names.
809 * The value of a recursively expanded variable is now expanded when putting
810 it into the environment for child processes. This change was made for
811 compatibility with Unix make.
813 * A rule with no targets before the `:' is now accepted and ignored.
814 This change was made for compatibility with SunOS 4 make.
815 We do not recommend that you write your makefiles to take advantage of this.
817 * The `-I' switch can now be used in MAKEFLAGS, and are put there
818 automatically just like other switches.
822 * Built-in rules for C++ source files with the `.C' suffix.
823 We still recommend that you use `.cc' instead.
825 * If a recipe is given too many times for a single target, the last one
826 given is used, and a warning message is printed.
828 * Error messages about makefiles are in standard GNU error format,
829 so C-x ` in Emacs works on them.
831 * Dependencies of pattern rules which contain no % need not actually exist
832 if they can be created (just like dependencies which do have a %).
836 * A message is always printed when Make decides there is nothing to be done.
837 It used to be that no message was printed for top-level phony targets
838 (because "`phony' is up to date" isn't quite right). Now a different
839 message "Nothing to be done for `phony'" is printed in that case.
841 * Archives on AIX now supposedly work.
843 * When the recipes specified for .DEFAULT are used to update a target,
844 the $< automatic variable is given the same value as $@ for that target.
845 This is how Unix make behaves, and this behavior is mandated by POSIX.2.
849 * The -n, -q, and -t options are not put in the `MAKEFLAGS' and `MFLAG'
850 variables while remaking makefiles, so recursive makes done while remaking
851 makefiles will behave properly.
853 * If the special target `.NOEXPORT' is specified in a makefile,
854 only variables that came from the environment and variables
855 defined on the command line are exported.
859 * Suffix rules may have dependencies (which are ignored).
863 * Dependencies of the form `-lLIB' are searched for as /usr/local/lib/libLIB.a
864 as well as libLIB.a in /usr/lib, /lib, the current directory, and VPATH.
868 * There is now a Unix man page for GNU Make. It is certainly not a
869 replacement for the Texinfo manual, but it documents the basic
870 functionality and the switches. For full documentation, you should
871 still read the Texinfo manual. Thanks to Dennis Morse of Stanford
872 University for contributing the initial version of this.
874 * Variables which are defined by default (e.g., `CC') will no longer be
875 put into the environment for child processes. (If these variables are
876 reset by the environment, makefiles, or the command line, they will
877 still go into the environment.)
879 * Makefiles which have recipes but no dependencies (and thus are always
880 considered out of date and in need of remaking), will not be remade (if they
881 were being remade only because they were makefiles). This means that GNU
882 Make will no longer go into an infinite loop when fed the makefiles that
883 `imake' (necessary to build X Windows) produces.
885 * There is no longer a warning for using the `vpath' directive with an explicit
886 pathname (instead of a `%' pattern).
890 * When removing intermediate files, only one `rm' command line is printed,
891 listing all file names.
893 * There are now automatic variables `$(^D)', `$(^F)', `$(?D)', and `$(?F)'.
894 These are the directory-only and file-only versions of `$^' and `$?'.
896 * Library dependencies given as `-lNAME' will use "libNAME.a" in the current
897 directory if it exists.
899 * The automatic variable `$($/)' is no longer defined.
901 * Leading `+' characters on a recipe line make that line be executed even
902 under -n, -t, or -q (as if the line contained `$(MAKE)').
904 * For recipe lines containing `$(MAKE)', `${MAKE}', or leading `+' characters,
905 only those lines are executed, not the entire recipe.
906 (This is how Unix make behaves for lines containing `$(MAKE)' or `${MAKE}'.)
910 * Filenames in rules will now have ~ and ~USER expanded.
912 * The `-p' output has been changed so it can be used as a makefile.
913 (All information that isn't specified by makefiles is prefaced with comment
918 * The % character can be quoted with backslash in implicit pattern rules,
919 static pattern rules, `vpath' directives, and `patsubst', `filter', and
920 `filter-out' functions. A warning is issued if a `vpath' directive's
921 pattern contains no %.
923 * The `wildcard' variable expansion function now expands ~ and ~USER.
925 * Messages indicating failed recipe lines now contain the target name:
926 make: *** [target] Error 1
928 * The `-p' output format has been changed somewhat to look more like
929 makefile rules and to give all information that Make has about files.
935 * The `-l' switch with no argument removes any previous load-average limit.
937 * When the `-w' switch is in effect, and Make has updated makefiles,
938 it will write a `Leaving directory' message before re-executing itself.
939 This makes the `directory change tracking' changes to Emacs's compilation
940 commands work properly.
944 * The automatic variable `$*' is now defined for explicit rules,
945 as it is in Unix make.
949 * The `-j' switch is now put in the MAKEFLAGS and MFLAGS variables when
950 specified without an argument (indicating infinite jobs).
951 The `-l' switch is not always put in the MAKEFLAGS and MFLAGS variables.
953 * Make no longer checks hashed directories after running recipes.
954 The behavior implemented in 3.41 caused too much slowdown.
958 * A dependency is NOT considered newer than its dependent if
959 they have the same modification time. The behavior implemented
960 in 3.43 conflicts with RCS.
964 * Dependency loops are no longer fatal errors.
966 * A dependency is considered newer than its dependent if
967 they have the same modification time.
971 * The variables F77 and F77FLAGS are now set by default to $(FC) and
972 $(FFLAGS). Makefiles designed for System V make may use these variables in
973 explicit rules and expect them to be set. Unfortunately, there is no way to
974 make setting these affect the Fortran implicit rules unless FC and FFLAGS
975 are not used (and these are used by BSD make).
979 * Make now checks to see if its hashed directories are changed by recipes.
980 Other makes that hash directories (Sun, 4.3 BSD) don't do this.
984 * The `shell' function no longer captures standard error output.
988 * A file beginning with a dot can be the default target if it also contains
989 a slash (e.g., `../bin/foo'). (Unix make allows this as well.)
993 * Archive member names are truncated to 15 characters.
995 * Yet more USG stuff.
997 * Minimal support for Microport System V (a 16-bit machine and a
998 brain-damaged compiler). This has even lower priority than other USG
999 support, so if it gets beyond trivial, I will take it out completely.
1001 * Revamped default implicit rules (not much visible change).
1003 * The -d and -p options can come from the environment.
1007 * Improved support for USG and HPUX (hopefully).
1009 * A variable reference like `$(foo:a=b)', if `a' contains a `%', is
1010 equivalent to `$(patsubst a,b,$(foo))'.
1012 * Defining .DEFAULT with no deps or recipe clears its recipe.
1014 * New default implicit rules for .S (cpp, then as), and .sh (copy and
1015 make executable). All default implicit rules that use cpp (even
1016 indirectly), use $(CPPFLAGS).
1020 * Giving the -j option with no arguments gives you infinite jobs.
1024 * New option: "-l LOAD" says not to start any new jobs while others are
1025 running if the load average is not below LOAD (a floating-point number).
1027 * There is support in place for implementations of remote command execution
1028 in Make. See the file remote.c.
1032 * No more than 10 directories will be kept open at once.
1033 (This number can be changed by redefining MAX_OPEN_DIRECTORIES in dir.c.)
1037 * Archive files will have their modification times recorded before doing
1038 anything that might change their modification times by updating an archive
1043 * The `MAKELEVEL' variable is defined for use by makefiles.
1047 * The recursion level indications in error messages are much shorter than
1048 they were in version 3.14.
1052 * Leading spaces before directives are ignored (as documented).
1054 * Included makefiles can determine the default goal target.
1055 (System V Make does it this way, so we are being compatible).
1059 * Variables that are defaults built into Make will not be put in the
1060 environment for children. This just saves some environment space and,
1061 except under -e, will be transparent to sub-makes.
1063 * Error messages from sub-makes will indicate the level of recursion.
1065 * Hopefully some speed-up for large directories due to a change in the
1066 directory hashing scheme.
1068 * One child will always get a standard input that is usable.
1070 * Default makefiles that don't exist will be remade and read in.
1074 * Count parentheses inside expansion function calls so you can
1075 have nested calls: `$(sort $(foreach x,a b,$(x)))'.
1079 * Several bug fixes, including USG and Sun386i support.
1081 * `shell' function to expand shell commands a la `
1083 * If the `-d' flag is given, version information will be printed.
1085 * The `-c' option has been renamed to `-C' for compatibility with tar.
1087 * The `-p' option no longer inhibits other normal operation.
1089 * Makefiles will be updated and re-read if necessary.
1091 * Can now run several recipes at once (parallelism), -j option.
1093 * Error messages will contain the level of Make recursion, if any.
1095 * The `MAKEFLAGS' and `MFLAGS' variables will be scanned for options after
1098 * A double-colon rule with no dependencies will always have its recipe run.
1099 (This is how both the BSD and System V versions of Make do it.)
1103 (Changes from versions 1 through 3.05 were never recorded. Sorry.)
1105 -------------------------------------------------------------------------------
1106 Copyright (C) 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1997,
1107 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
1108 2010 Free Software Foundation, Inc. This file is part of GNU Make.
1110 GNU Make is free software; you can redistribute it and/or modify it under the
1111 terms of the GNU General Public License as published by the Free Software
1112 Foundation; either version 3 of the License, or (at your option) any later
1115 GNU Make is distributed in the hope that it will be useful, but WITHOUT ANY
1116 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR
1117 A PARTICULAR PURPOSE. See the GNU General Public License for more details.
1119 You should have received a copy of the GNU General Public License along with
1120 this program. If not, see <http://www.gnu.org/licenses/>.