[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: too-aggressive clean rule
From: |
John Darrington |
Subject: |
Re: too-aggressive clean rule |
Date: |
Fri, 9 Oct 2009 08:54:16 +0000 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
On Thu, Oct 08, 2009 at 08:10:57PM -0700, Ben Pfaff wrote:
Commit 99bafccc08919a5d640cb35962c4d730a2cad3a1 "Fix make
distcheck" introduces the following:
# This seems to be necessary as the libtool artifacts aren't removed
# Automake bug ?
tests_data_datasheet_test_CLEAN:
$(RM) -r tests/data
Clearly this rule is far too promiscuous. I seem to remember it was a kludge
to work around a problem. Various .lib directories were not getting removed.
Thus, the make distcheck rule failed.
There are a couple of problems with this. First, $(RM) isn't
defined on every system, and so sometimes it expands to the null
string. I'm not sure where it's defined, in fact, but Automake
itself just uses "rm" all over, so I'm sure that it's OK to use
plain "rm". Second, if you run configure" in the source
directory then this deletes datasheet-test.c and
datasheet-test.sh, which is obviously a bad idea. Finally, I
think that -f is warranted in case the files in question haven't
been built.
I always understood that $(RM) should be prefered. It expands to "rm -f"
on POSIX systems an "DEL /Y" on windoze.
--
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://pgp.mit.edu or any PGP keyserver for public key.
signature.asc
Description: Digital signature