This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: Avoid `touch' in Makefiles
- To: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Subject: Re: PATCH: Avoid `touch' in Makefiles
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 13 May 2001 17:47:48 -0300
- Cc: Mark Mitchell <mark at codesourcery dot com>, <gcc-patches at gcc dot gnu dot org>, Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Organization: GCC Team, Red Hat
- References: <Pine.LNX.4.33.0105132106030.12089-100000@kern.srcf.societies.cam.ac.uk>
On May 13, 2001, "Joseph S. Myers" <jsm28@cam.ac.uk> wrote:
> On Sun, 13 May 2001, Mark Mitchell wrote:
>> $(srcdir)/gcov.1: $(srcdir)/gcov.texi
>> ! touch $(srcdir)/gcov.1
>> -$(TEXI2POD) < $(srcdir)/gcov.texi > gcov.pod
>> -($(POD2MAN) gcov.pod > $(srcdir)/gcov.1.T$$$$ && \
>> mv -f $(srcdir)/gcov.1.T$$$$ $(srcdir)/gcov.1) || \
>> --- 2314,2320 ----
>> generated-manpages: $(srcdir)/gcov.1 $(srcdir)/cpp.1 $(srcdir)/gcc.1
>>
>> $(srcdir)/gcov.1: $(srcdir)/gcov.texi
>> ! $(STAMP) $(srcdir)/gcov.1
> This touch isn't for a dummy timestamp file, but I don't understand what
> purpose it (added by dj on the 17th of January) serves anyway
I'd guess the point is to get the rule to not fail again next time, in
case TEXI2POD or POD2MAN are missing or fail. Not that I like this
kind of unreproducible build problem.
Using $(STAMP) here is fine, though, since the file is going to be
overwritten if the build succeeds, anyway.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me