On Friday 22 March 2002 10:32 am, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
> | Why don't I upgrade very often? Because I then have to spend an entire
> | day tracking down the bugs in the new software! In this case the
> | dependency tracker used by the new automake/autoconf is broken for Tru64.
> | I have now fixed it so that all works correctly.
> |
> | Perhaps someone who knows would forward this fix to the correct list.
> |
> | Anyone have any objections if I apply it to config/depcomp in our own
> | tree?
>
> do we have a depcomp in our tree?
>
> Hmm, yes we do... Should we, or should we let automake automatically
> copy this in?
>
> I have no objections, but I'd also like to see a patch against the
> regular depcomp.

Jean-Marc added this file to the repository fairly recently.


On my machine I have just installed automake 1.5. It's version of depcomp 
contains:

   # The Tru64 AIX compiler uses -MD to generate dependencies as a side
   # effect.  `cc -MD -o foo.o ...' puts the dependencies into `foo.o.d'.
   # At least on Alpha/Redhat 6.1, Compaq CCC V6.2-504 seems to put
   # dependencies in `foo.d' instead, so we check for that too.
   # Subdirectories are respected.

   tmpdepfile1="$object.d"
   tmpdepfile2=`echo "$object" | sed -e 's/.o$/.d/'`
   if test "$libtool" = yes; then
      "$@" -Wc,-MD
   else
      "$@" -MD
   fi

so, you see, this contains the bug too.

As I see it, the automake list needs to be informed, and in the meantime we 
should use our patched version of depcomp.

Can I leave this with you please. 

Angus



Reply via email to