diff options
| -rw-r--r-- | NEWS | 8 | ||||
| -rw-r--r-- | README.template | 62 | ||||
| -rw-r--r-- | config/Makefile.am | 5 |
3 files changed, 41 insertions, 34 deletions
@@ -26,9 +26,9 @@ Version 3.80 This syntax is only valid within explicit and static pattern rules: it cannot be used in implicit (suffix or pattern) rules. Edouard G. Parmelan <egp@free.fr> provided a patch implementing this feature; however, I - decided to implemented it in a different way. + decided to implement it in a different way. -* A new function is defined: $(quote ...). The argument to this +* A new function is defined: $(value ...). The argument to this function is the _name_ of a variable. The result of the function is the value of the variable, without having been expanded. @@ -59,6 +59,10 @@ Version 3.80 variables. This may mean that if you added extra escaping to your $(call ...) function arguments you will need to undo it now. +* The variable invoked by $(call ...) can now be recursive: unlike other + variables it can reference itself and this will not produce an error + when it is used as the first argument to $(call ...) (but only then). + * New pseudo-target .LOW_RESOLUTION_TIME, superseding the configure option --disable-nsec-timestamps. You might need this if your build process depends on tools like "cp -p" preserving time stamps, since diff --git a/README.template b/README.template index 9912ffd..969f208 100644 --- a/README.template +++ b/README.template @@ -108,6 +108,37 @@ repository: it is not unheard of for code that is known to be broken to be checked in. Use at your own risk. +System-specific Notes +--------------------- + +It has been reported that the XLC 1.2 compiler on AIX 3.2 is buggy such +that if you compile make with `cc -O' on AIX 3.2, it will not work correctly. +It is said that using `cc' without `-O' does work. + +One area that is often a problem in configuration and porting is the code +to check the system's current load average. To make it easier to test and +debug this code, you can do `make check-loadavg' to see if it works +properly on your system. (You must run `configure' beforehand, but you +need not build Make itself to run this test.) + +Another potential source of porting problems is the support for large +files (LFS) in configure for those operating systems that provide it. +Please report any bugs that you find in this area. If you run into +difficulties, then as a workaround you should be able to disable LFS by +adding the `--disable-largefile' option to the `configure' script. + +On systems that support micro- and nano-second timestamp values and +where stat(2) provides this information, GNU make will use it when +comparing timestamps to get the most accurate possible result. However, +note that many current implementations of tools that *set* timestamps do +not preserve micro- or nano-second granularity. This means that "cp -p" +and other similar tools (tar, etc.) may not exactly duplicate timestamps +with micro- and nano-second granularity on some systems. If your build +system contains rules that depend on proper behavior of tools like "cp +-p", you should consider using the .LOW_RESOLUTION_TIME pseudo-target to +force make to treat them properly. See the manual for details. + + Ports ----- @@ -131,34 +162,3 @@ Please note there are two _separate_ ports of GNU make for Microsoft systems: a native Windows tool built with (for example) MSVC or Cygwin, and a DOS-based tool built with DJGPP. Please be sure you are looking at the right README! - - -System-specific Notes ---------------------- - -It has been reported that the XLC 1.2 compiler on AIX 3.2 is buggy such -that if you compile make with `cc -O' on AIX 3.2, it will not work correctly. -It is said that using `cc' without `-O' does work. - -One area that is often a problem in configuration and porting is the code -to check the system's current load average. To make it easier to test and -debug this code, you can do `make check-loadavg' to see if it works -properly on your system. (You must run `configure' beforehand, but you -need not build Make itself to run this test.) - -Another potential source of porting problems is the support for large -files (LFS) in configure for those operating systems that provide it. -Please report any bugs that you find in this area. If you run into -difficulties, then as a workaround you should be able to disable LFS by -adding the `--disable-largefile' option to the `configure' script. - -On systems that support micro- and nano-second timestamp values and -where stat(2) provides this information, GNU make will use it when -comparing timestamps to get the most accurate possible result. However, -at the moment there is no system call (that I'm aware of) that will -allow you to *set* a timestamp to a micro- or nano-second granularity. -This means that "cp -p" and other similar tools (tar, etc.) cannot -exactly duplicate timestamps with micro- and nano-second granularity. -If your build system contains rules that depend on proper behavior of -tools like "cp -p", you should configure make to not use micro- and -nano-second timestamps with the --disable-nsec-timestamps flag. diff --git a/config/Makefile.am b/config/Makefile.am index 60cca4c..1acf844 100644 --- a/config/Makefile.am +++ b/config/Makefile.am @@ -1 +1,4 @@ -EXTRA_DIST = codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4 lib-ld.m4 lib-link.m4 lib-prefix.m4 progtest.m4 +EXTRA_DIST = codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 \ + intdiv0.m4 inttypes-pri.m4 inttypes.m4 inttypes_h.m4 \ + isc-posix.m4 lcmessage.m4 lib-ld.m4 lib-link.m4 lib-prefix.m4 \ + progtest.m4 stdint_h.m4 uintmax_t.m4 ulonglong.m4 |