automake-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FYI: do not remove core dumps


From: Alexandre Duret-Lutz
Subject: FYI: do not remove core dumps
Date: Sun, 27 Jul 2003 14:58:25 +0200
User-agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (gnu/linux)

Following up to 
  http://sources.redhat.com/ml/automake/2003-02/msg00018.html

I'm installing this on HEAD.

2003-07-27  Alexandre Duret-Lutz  <address@hidden>

        * lib/am/compile.am (mostlyclean-compile): Do not erase core dumps.
        * automake.texi (Built sources example): Adjust example.

Index: NEWS
===================================================================
RCS file: /cvs/automake/automake/NEWS,v
retrieving revision 1.220
diff -u -r1.220 NEWS
--- NEWS        16 Jul 2003 19:10:06 -0000      1.220
+++ NEWS        27 Jul 2003 12:56:20 -0000
@@ -75,6 +75,10 @@
 
   - 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 @@
 
   - 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.
 
 
 New in 1.7:
Index: automake.texi
===================================================================
RCS file: /cvs/automake/automake/automake.texi,v
retrieving revision 1.346
diff -u -r1.346 automake.texi
--- automake.texi       16 Jul 2003 19:10:06 -0000      1.346
+++ automake.texi       27 Jul 2003 12:56:24 -0000
@@ -3819,7 +3819,7 @@
 % 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 \
Index: lib/am/compile.am
===================================================================
RCS file: /cvs/automake/automake/lib/am/compile.am,v
retrieving revision 1.30
diff -u -r1.30 compile.am
--- lib/am/compile.am   2 Jun 2003 07:08:40 -0000       1.30
+++ lib/am/compile.am   27 Jul 2003 12:56:24 -0000
@@ -21,9 +21,7 @@
 
 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

-- 
Alexandre Duret-Lutz





reply via email to

[Prev in Thread] Current Thread [Next in Thread]