Re: [PATCH] depcomp and gcc3 still not safe enough

[Raja R Harinath]

Hi,

Raja R Harinath <address@hidden> writes:
> GCC 3.0 doesn't still exactly implement exactly what 'depcomp' wants.
> 
> The problem is that if the compile fails, the file specified to -MF is
> deleted too.  With 'gcc -MF $depfile', $depfile is deleted.  But,
> $depfile is eventually included by the Makefile -- so subsequent
> 'make' invocations will fail, since an included file doesn't exist.
[snip]
>       * depcomp (gcc3): Protect against the compiler deleting 
>       the dependency output file.
[snip]

(Sorry to followup to myself).

A more elaborate solution (assuming the GCC behaviour is not a bug),
is to 

  1. copy the old 'gcc3' code to a 'gcc3-unsafe' mode

  2. apply the above patch to the 'gcc3' part

  3. extend the 'make' include/.include detection to also search for
     'sinclude/-include' keywords

  4. If 'gcc3' and 'sinclude/-include' are supported, change $depmode
     to 'gcc3-unsafe', and don't bother creating the dummy .Plo files
     in config.status

I'm not sure it's worth the bother :-)  

- Hari
-- 
Raja R Harinath ------------------------------ address@hidden
"When all else fails, read the instructions."      -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing."   -- Roy L Ash