Re: More about dependencies...

[Robert Boehne]

I have a similar problem, I have 'depcomp' in
$(top_srcdir)/make
and I have used
AC_CONFIG_AUX_DIR(make)
in 'configure.in'.  This doesn't work, but if I copy 'depcomp'
into $(top_srcdir) then it works.  Is there another step required
to get automake to find these auxiliary scripts?
I'm using CVS versions of Automake, Autoconf and Libtool (MLB).


Raja R Harinath wrote:
> 
> Patrick Guio <address@hidden> writes:
> > I refer to my earlier mails about problem with c++ dependencies. I don't
> > know whether this is a bug but I found out why I could not make
> > dependencies tracking working correctly.
> > My code consists of several directories
> >
> > ~
> > ~/src
> > ~/tests
> > and so on
> >
> > ~/Makefile.am does not contain so much
> > ~/src is a directory with common c++ headers and source codes  while
> > ~/tests contains source codes to build and test.
> >
> > When I run automake (-a -c --include-deps --force-missing) 'depcomp' were
> > installed in ~/src and ~/tests but *not* in ~
> > And there is the problem: when running configure I always got the messages
> >
> > checking dependency style of g++... none
> > checking dependency style of gcc... none
> >
> > until I manually add a ~/depcomp
> >
> > Then
> >
> > checking dependency style of g++... gcc
> > checking dependency style of gcc... gcc
> >
> > Why is a ~/depcomp necessary in ~/ since I don't have any code there?
> 
> Actually it is needed only there, and not in the source directories.
> You just need one copy of the script per tree.  'automake' appears to
> be buggy.
> 
> - 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

-- 
Robert Boehne             Software Engineer
Ricardo Software   Chicago Technical Center
TEL: (630)789-0003 x. 238
FAX: (630)789-0127
email:  address@hidden