Paul Eggert <egg...@cs.ucla.edu> writes: > I don't see how adding a dependency would fix this problem. In this > case, lib/Makefile in turn depended on 'configure', 'configure.in', > 'm4/longlong.m4', etc., etc., and one of these files got updated, so > lib/Makefile was regenerated; but as I understand it, the 'make' that was > (still) running was based on the out-of-date lib/Makefile, and it > generated the a bad lib/unistd.h.
Looks like an orderring problem. Normally, if GNU make sees that a makefile is remade it rereads it automatically. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
