diff options
Diffstat (limited to 'NEWS')
| -rw-r--r-- | NEWS | 64 |
1 files changed, 9 insertions, 55 deletions
@@ -1,6 +1,6 @@ GNU make NEWS -*-indented-text-*- History of user-visible changes. - 17 April 2011 + 28 July 2010 See the end of this file for copyrights and conditions. @@ -9,45 +9,6 @@ manual, which is contained in this distribution as the file doc/make.texi. See the README file and the GNU make manual for instructions for reporting bugs. -Version 3.82.90 - -A complete list of bugs fixed in this version is available here: - -http://sv.gnu.org/bugs/index.php?group=make&report_id=111&fix_release_id=101&set=custom - -* WARNING: Backward-incompatibility! - This version of make adheres to the POSIX backslash/newline handling, - introducing the following differences: - * Each backslash/newline in a variable value is replaced with a space; - multiple consecutive backslash/newlines do not condense into one space. - * In recipes, a recipe prefix following a backslash-newlines is removed. - -* New feature: The "job server" capability is now supported on Windows. - Implementation contributed by Troy Runkel <Troy.Runkel@mathworks.com> - -* New feature: "!=" shell assignment operator as an alternative to the - $(shell ...) function. Implemented for compatibility with BSD makefiles. - WARNING: Backward-incompatibility! - Variables ending in "!" previously defined as "variable!= value" will now be - interpreted as shell assignment. Change your assignment to add whitespace - between the "!" and "=": "variable! = value" - -* New command line option: --trace enables tracing of targets. When enabled - the recipe to be invoked is printed even if it would otherwise be suppressed - by .SILENT or a "@" prefix character. Also before each recipe is run the - makefile name and linenumber where it was defined are shown as well as the - prerequisites that caused the target to be considered out of date. - -* On failure, the makefile name and linenumber of the recipe that failed are - shown. - -* A .RECIPEPREFIX setting is remembered per-recipe and variables expanded - in that recipe also use that recipe prefix setting. - -* In -p output, .RECIPEPREFIX settings are shown and all target-specific - variables are output as if in a makefile, instead of as comments. - - Version 3.82 A complete list of bugs fixed in this version is available here: @@ -57,6 +18,14 @@ http://sv.gnu.org/bugs/index.php?group=make&report_id=111&fix_release_id=104&set * Compiling GNU make now requires a conforming ISO C 1989 compiler and standard runtime library. +* WARNING: Future backward-incompatibility! + Wildcards are not documented as returning sorted values, but up to and + including this release the results have been sorted and some makefiles are + apparently depending on that. In the next release of GNU make, for + performance reasons, we may remove that sorting. If your makefiles + require sorted results from wildcard expansions, use the $(sort ...) + function to request it explicitly. + * WARNING: Backward-incompatibility! The POSIX standard for make was changed in the 2008 version in a fundamentally incompatible way: make is required to invoke the shell as if @@ -73,21 +42,6 @@ http://sv.gnu.org/bugs/index.php?group=make&report_id=111&fix_release_id=104&set existing targets were provided in $?). * WARNING: Backward-incompatibility! - Wildcards were not documented as returning sorted values, but the results - have been sorted up until this release.. If your makefiles require sorted - results from wildcard expansions, use the $(sort ...) function to request - it explicitly. - -* WARNING: Backward-incompatibility! - In previous versions of make it was acceptable to list one or more explicit - targets followed by one or more pattern targets in the same rule and it - worked "as expected". However, this was not documented as acceptable and if - you listed any explicit targets AFTER the pattern targets, the entire rule - would be mis-parsed. This release removes this ability completely: make - will generate an error message if you mix explicit and pattern targets in - the same rule. - -* WARNING: Backward-incompatibility! As a result of parser enhancements, three backward-compatibility issues exist: first, a prerequisite containing an "=" cannot be escaped with a backslash any longer. You must create a variable containing an "=" and |