A possible bug (or a feature) : dependencies shown in dry-run but not rebuilt

2002-11-13 Thread David Mentre
Hello, I don't know if it is a bug or a feature, but I observe a strange behavior with a makefile of my own. You'll find the Makefile as well as needed dummy file in the attachement. For this project, if a make a 'make' on an empty directory, everything is made correctly. However, if I modify

make segmentation fault

2002-11-13 Thread Edward Welbourne
I'm using GNU make from within GNU emacs using M-x compile. A (buggy) Makefile containing only: quote src=Makefile PACKAPPS = simple $(PACKAPPS:%=pack-index-dt-%): echo 'dt id=$(@:pack-index-dt-%:%)' \ 'a href=$(@:pack-index-dt-%:%)$(@:pack-index-dt-%:%)/a' \

Re: make segmentation fault

2002-11-13 Thread Paul D. Smith
This bug is fixed in the latest version, GNU make 3.80. Please try that and let us know if it doesn't work. Thanks for the report! -- --- Paul D. Smith [EMAIL PROTECTED] Find some GNU make tips at:

Re: A possible bug (or a feature) : dependencies shown in dry-run but not rebuilt

2002-11-13 Thread Paul D. Smith
I tried your environment on my Debian GNU/Linux box with GNU make 3.79.1 and it worked fine for me: when I ran make everything was rebuilt and when I ran make x.o, x.o was rebuilt. It didn't say they were up to date. There must be something else about your environment that's causing this

RE: A possible bug (or a feature) : dependencies shown in dry-run but not rebuilt

2002-11-13 Thread David Mentre
Hello Mr Smith, -Original Message- From: Paul D. Smith [mailto:psmith;gnu.org] Sent: mercredi 13 novembre 2002 16:17 I tried your environment on my Debian GNU/Linux box with GNU make 3.79.1 and it worked fine for me: when I ran make everything was rebuilt and when I ran make

RE: A possible bug (or a feature) : dependencies shown in dry-run but not rebuilt

2002-11-13 Thread Paul D. Smith
%% David Mentre [EMAIL PROTECTED] writes: dmPrerequisite `x.h' is newer than target `x.c'. ok No, not OK! You don't want to specify that the .c file depends on the .h file. You don't update the .c file when the .h file changes: you have no rule for that. It's the .o file that