Re: semantics of .DELETE_ON_ERROR

2000-07-05 Thread Paul D. Smith
%% Raymond Nijssen <[EMAIL PROTECTED]> writes: rn> ::: "PDS" == Paul D Smith <[EMAIL PROTECTED]> writes: >> %% Raymond Nijssen <[EMAIL PROTECTED]> writes: rn> As a result, my .a files are not deleted if a .o file fails to rn> compile, and then my executable will link happily in a recurs

Re: semantics of .DELETE_ON_ERROR

2000-07-05 Thread Raymond Nijssen
::: "PDS" == Paul D Smith <[EMAIL PROTECTED]> writes: > %% Raymond Nijssen <[EMAIL PROTECTED]> writes: rn> As a result, my .a files are not deleted if a .o file fails to rn> compile, and then my executable will link happily in a recursive rn> make environment. This is undesired. > That me

Re: semantics of .DELETE_ON_ERROR

2000-07-05 Thread Paul D. Smith
%% Raymond Nijssen <[EMAIL PROTECTED]> writes: rn> As a result, my .a files are not deleted if a .o file fails to rn> compile, and then my executable will link happily in a recursive rn> make environment. This is undesired. That means your recursive make environment isn't set up correctly

semantics of .DELETE_ON_ERROR

2000-07-05 Thread Raymond Nijssen
Hi, When an error occurs in a rule, make will not delete the target if the timestamp has not changed. As a result, my .a files are not deleted if a .o file fails to compile, and then my executable will link happily in a recursive make environment. This is undesired. The makefile looks like: -