Re: Libtool convenience library dependence check

[Bob Friesenhahn]

On Mon, 23 Aug 2004, Andre Caldas wrote:

> > > I am using --disable-dependency-tracking as a configure option to avoid 
> > > this problem. What kind of dependency can I expect to fail with this?
> >
> >
> > If you edit a source file and add or remove a header file inclusion, then 
> > make will not notice the change so it may produce bad results. If you are 
> > using a distributed package, then the Makefile should include the existing 
> > dependency information within itself.  If you bootstrapped from scratch, 
> > then there may be not header dependency information at all.
>
> Does it means that some prog.o will only be tested against some prog.cpp? All 
> the other dependencies would be ignored... (or not even that?)

If the Makefile was produced as a result of 'make dist' then it will 
include the dependencies existing when the distribution was produced. 
Otherwise prog.o will depend only on prog.cpp.  While ok for one time 
builds, it is not ok for developers.

> Anyway, my initial problem is still there: "make install" will recompile 
> every .cpp file in a convenience library even if no file (in the whole 
> package) was edited! Can I call libtool a "obscure linker"?

Could it be that you have a timestamp problem?  Are all files on local 
disk, or are you using a network?  Unless time keeping is closely 
managed (e.g. via NTP) mixing files between local disk and a server 
over the network can give make fits.

Bob
======================================
Bob Friesenhahn
address@hidden
http://www.simplesystems.org/users/bfriesen