[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug when specifying --disable-dependency-tracking (AM_DEP_TRACK)

From: Alexandre Oliva
Subject: Re: Bug when specifying --disable-dependency-tracking (AM_DEP_TRACK)
Date: 19 Apr 2001 17:49:01 -0300
User-agent: Gnus/5.090002 (Oort Gnus v0.02) XEmacs/21.1 (Cuyahoga Valley)

On Apr 18, 2001, Robert Boehne <address@hidden> wrote:

> .c.o:
>       source='$<' object='$@' libtool=no @AMDEPBACKSLASH@
>       depfile='$(DEPDIR)/$*.Po' tmpdepfile='$(DEPDIR)/$*.TPo'
>       $(CCDEPMODE) $(depcomp) @AMDEPBACKSLASH@
>       $(COMPILE) -c -o $@ `test -f $< || echo '$(srcdir)/'`$<

AFAICT, this was not generated by the automake that corresponds to the
new m4/depend.m4.  The new version should have `#'s in the beginning
of the lines containing AMDEPBACKSLASH.  This should have been a
result of the new if/endif AMDEP rules in

However, I see the change that introduced AMDEP as a conditional has
removed the test for the existence of the depcomp script.  Hmm...
Perhaps this is not necessary, since this very script is used to
choose a dependency tracking mechanism, so we'd end up with `no' if it
doesn't exist.  Yeah, that makes sense...

Alexandre Oliva   Enjoy Guarana', see
Red Hat GCC Developer                  address@hidden,}
CS PhD student at IC-Unicamp        address@hidden,}
Free Software Evangelist    *Please* write to mailing lists, not to me

reply via email to

[Prev in Thread] Current Thread [Next in Thread]