From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
Suppose that, for some reason, I get into a state where my foo.h file is older
than my foo.y file, but my foo.c file is up-to-date.
This happened to me when I had a piece of software stored in a version control
system, and the original authors had placed foo.c, foo.h, and foo.y all into the
version control system.
So when I did make, the following rule fired
@if test ! -f $@; then \
rm -f foo.c; \
$(MAKE) foo.c; \
else :; fi
Since foo.h was older than foo.c, the rule fired.
But since foo.h existed, nothing happened.
I am not sure the best way to fix this. One approach might be to fix it for
bison. Thus if yacc=bison then generate
%.c %.h: %.y
and get rid of all the nonsense about ylwrap.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Take a yacc file, foo.y
2. make foo.c
3. touch foo.y
4. touch foo.c
Actual Results: On step 5, nothing is remade, even though foo.h is older than foo.y
Expected Results: foo.h should have been rebuilt.
The version of Automake in RHL 7.3 is rather old.
Could you please try with a newer version?
If you can reproduce with recent/current automake,
then could you please attach some example tarball to help
test this problem?
Anyway I suggest taking this issue upstream to one of the automake
lists if it is still present in Automake 1.8.
Is it possible you could provide a small testcase for this, please?
That would make it easier to look into?
If this is still an issue with the latest automake, please resubmit
your bug report to <firstname.lastname@example.org>. Thanks.