Thanks, I will try that. I have one more question. I see that if I do a ctrl c then fatal_error_signal function is called.
Now the problem is if I am trapping ctrl c in makefile then fatal_error_signal is not called... Is this expected? I want to trap the signal in makefile to print the status. Also I want to catch the signal in make code as I am doing some processing there like deleting temp files etc.. What is the sequence of catching signal? Please help. On Mon, 21 Oct 2019, 10:47 Paul Smith, <psm...@gnu.org> wrote: > On Mon, 2019-10-21 at 10:11 +0530, nikhil jain wrote: > > Alright, so I don't know much of the makefile stuff. But can it happen > like a makefile is more optimized for a specific make version ? > > Can that happen at all? > > > I don't know how to answer this question in a useful way. Of course, it's > possible. Almost anything is possible. > > You might try using the latest release candidate for GNU make 4.3 and see > if it helps. Maybe some bug fixed since 4.2 was released is impacting your > build: > > https://alpha.gnu.org/gnu/make/make-4.2.92.tar.gz > _______________________________________________ Help-make mailing list Help-make@gnu.org https://lists.gnu.org/mailman/listinfo/help-make
