[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ensure that generated files are read-only
From: |
Paul Eggert |
Subject: |
Re: ensure that generated files are read-only |
Date: |
Thu, 07 Sep 2006 11:00:20 -0700 |
User-agent: |
Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) |
Ralf Wildenhues <address@hidden> writes:
>> alloca.h: alloca_.h
>> $(LN_F_S) $(srcdir)/alloca_.h $@
>>
>> where $(LN_FS) expands to "ln -fs" in the typical case, or to
>> "rm -f $@ && cp" on hosts where "ln -fs" doesn't work (e.g., Solaris 9
>> and earlier).
>
> I like it, but it runs a bit contrary to command optimization; for
> example, the HP-UX make I tested will try to update the symlink target
> upon every invocation, not just the first one.
Ouch. Well, I suppose we can test for that performance bug too, and
use the fallback expansion on HP-UX as well.
Re: ensure that generated files are read-only, Jim Meyering, 2006/09/08
Re: [bug-gnulib] ensure that generated files are read-only, Bruno Haible, 2006/09/07
- Re: ensure that generated files are read-only, Simon Josefsson, 2006/09/07
- Re: ensure that generated files are read-only, Simon Josefsson, 2006/09/07
- Re: ensure that generated files are read-only, Ralf Wildenhues, 2006/09/07
- Re: ensure that generated files are read-only, Bruce Korb, 2006/09/07
- Re: ensure that generated files are read-only, Simon Josefsson, 2006/09/07
- Re: ensure that generated files are read-only, Ralf Wildenhues, 2006/09/07
- Re: ensure that generated files are read-only, Simon Josefsson, 2006/09/07