> Hello,
Hi,
> The usual workaround to add prerequisites to an automake-generated
> rule is to use a one-off make variable for the target name. For
> example,
>
> doc_bison_dvi = doc/bison.dvi
> $(doc_bison_dvi): $(FIGS_DOT:.dot=.eps)
>
> and so on. Automake does a simple string comparison
Hi Theophile, nick.
On 12/06/2012 11:16 PM, Nick Bowler wrote:
> Hello,
>
> On 2012-12-06 16:41 +0100, Theophile Ranquet wrote:
>> I am seeking advice for a workaround of what seems like a limitation
>> in Automake (1.12.2).
>>
>> We have recently added figures to Bison's documentation. These fig
On Thu, 6 Dec 2012, Philip Guenther wrote:
> Note that this problem doesn't arise on systems with high precision
> file timestamps. Many systems have provided those since the mid 90's;
> I'm appalled that the modern system that process the involved shell
> commands fast enough for this to regul
On Thu, 6 Dec 2012, Philip Guenther wrote:
> On Thu, Dec 6, 2012 at 2:02 PM, Mikulas Patocka
> wrote:
> > The apparent problem is that after make rebuilds b, it compares b's time
> > with a's time, finds that the times are equal (because a was touched just
> > before make was run) and doesn't r
On Thu, Dec 6, 2012 at 2:02 PM, Mikulas Patocka
wrote:
> The apparent problem is that after make rebuilds b, it compares b's time
> with a's time, finds that the times are equal (because a was touched just
> before make was run) and doesn't rebuild a.
>
> I think it is a bug - when b is finished,
Hi
Try this Makefile:
---
a : b
echo build a
touch a
b : c
echo build b
touch b
---
and run this script:
touch b;sleep 1;touch a c;make
You see
"echo build b
build b
touch b"
but it doesn't remake a.
The apparent problem is that after make rebuilds b, it compares
