nested relative path in include not handled as in other makes

2001-01-17 Thread Kanda Kumaravel
Problem : when the make file has a relative path like "../head1.mk" and if the file head1.mk has another include which is relative to its own position like "../head2.mk" then running the make on top make file reports an error like "../head2.mk" not found. example : In the includ

Re: Better Debugging

2001-01-17 Thread Paul D. Smith
%% Regarding Better Debugging; you wrote: jlp> The -d debug flag gives some information, but not a lot. What jlp> I would like to be able to see is: Some would say it gives too much :) jlp> (a) the values of all the variables jlp> (b) what files are being included jlp> (c) what the a

Better Debugging

2001-01-17 Thread James L. Peterson
A major problem that I have with make is being able to debug the makefiles. I end up working on big projects that are supposed to be for multiple platforms, so there are a lot of make variables and thousands of lines of multiple makefiles. My difficulty is in seeing what everything expands to, s

Re: *** not correct for time skew

2001-01-17 Thread Paul D. Smith
%% Regarding *** not correct for time skew; you wrote: k> In make's time skew warning message: k> make[2]: *** Warning: File `file' has modification time in the future k> (2001-01-16 05:55:30.3184 > 2001-01-16 05:55:30.170387819) k> I really strongly believe the *** should not be