* lib/am/compile.am (mostlyclean-compile): Do not erase core dumps.

* automake.texi (Built sources example): Adjust example.

diff --git a/ChangeLog b/ChangeLog
index 24aa2ced0a2fd3793008c438a3206265aa42f774..472346a561141a8655b8205ed8ba5fadd4162cd5 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2003-07-27  Alexandre Duret-Lutz  <adl@gnu.org>
+
+       * lib/am/compile.am (mostlyclean-compile): Do not erase core dumps.
+       * automake.texi (Built sources example): Adjust example.
+
 2003-07-26  Alexandre Duret-Lutz  <adl@gnu.org>
 
        * automake.in (get_object_extension, handle_languages)

diff --git a/NEWS b/NEWS
index a355ab079a050dc3d7f05957d42330e46f53efce..c3dd132f385951e4b935733f1a3954ac9a7569b0 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -75,6 +75,10 @@ New in 1.7a:
 
   - install-sh now understands --version and --help.
 
+  - Automake will now recognize AC_CONFIG_LINKS so far as removing created
+    links as part of the distclean target and including source files in
+    distributions.
+
 * Obsolete features
 
   - lisp_DATA is now allowed.  If you are using the empty ELCFILES
@@ -142,8 +146,17 @@ New in 1.7a:
 
   - Targets dist-gzip, dist-bzip2, dist-tarZ, dist-zip are always defined.
 
-* Automake will now recognize AC_CONFIG_LINKS so far as removing created links
-  as part of the distclean target and including source files in distributions.
+  - core dumps are no longer removed by the cleaning rules.  There are
+    at least three reasons for this:
+      1. These files should not be created by any build step,
+        so their removal do not fit any of the cleaning rules.
+        Actually, they may be precious to the developer.
+      2. If such file is created during a build, then it's clearly a
+         bug Automake should not hide.  Not removing the file will
+         cause `make distcheck' to complain about its presence.
+      3. Operating systems have different naming conventions for
+         core dump files.  A core file on one system might be a
+        completely legitimate data file on another system.
 
 \f
 New in 1.7:

diff --git a/automake.texi b/automake.texi
index 4e3bc0697957fd630560cfac75474988c774a1cd..4ba36df9759b372d01a289dcb219fc05a3ece5f5 100644 (file)
--- a/automake.texi
+++ b/automake.texi
@@ -3819,7 +3819,7 @@ if you try to run @code{make foo} explicitly:
 % make clean
 test -z "bindir.h" || rm -f bindir.h
 test -z "foo" || rm -f foo
-rm -f *.o core *.core
+rm -f *.o
 % : > .deps/foo.Po # Suppress previously recorded dependencies
 % make foo
 source='foo.c' object='foo.o' libtool=no \

diff --git a/lib/am/compile.am b/lib/am/compile.am
index bf594b1d4f54b64a8e2e5ca6bef2c1b503e5a578..aa1ed576b83f2dfc48f8c648a252b3cddcf00939 100644 (file)
--- a/lib/am/compile.am
+++ b/lib/am/compile.am
@@ -21,9 +21,7 @@ DEFAULT_INCLUDES = %DEFAULT_INCLUDES%
 
 mostlyclean-am: mostlyclean-compile
 mostlyclean-compile:
-## Don't remove 'core.*' because some distributions have eg "core.c".
-## 4.4BSD systems use `PROG.core'.
-       -rm -f *.$(OBJEXT) core *.core
+       -rm -f *.$(OBJEXT)
 ?MOSTLYRMS?%MOSTLYRMS%
 
 distclean-am: distclean-compile

diff --git a/stamp-vti b/stamp-vti
index 056422d0ce4cb47c9d528b4073d93cd4893c3cd3..24106ae96dadc1b85fbaae48ff77ee0944287670 100644 (file)
--- a/stamp-vti
+++ b/stamp-vti
@@ -1,4 +1,4 @@
-@set UPDATED 20 July 2003
+@set UPDATED 27 July 2003
 @set UPDATED-MONTH July 2003
 @set EDITION 1.7a
 @set VERSION 1.7a

diff --git a/version.texi b/version.texi
index 056422d0ce4cb47c9d528b4073d93cd4893c3cd3..24106ae96dadc1b85fbaae48ff77ee0944287670 100644 (file)
--- a/version.texi
+++ b/version.texi
@@ -1,4 +1,4 @@
-@set UPDATED 20 July 2003
+@set UPDATED 27 July 2003
 @set UPDATED-MONTH July 2003
 @set EDITION 1.7a
 @set VERSION 1.7a