On Sep 22, 2004, at 3:59 AM, Ralf Wildenhues wrote:
>> I have seen builds get out of whack like this a few times; I think
>> it's been due to situations like: - when you run configure multiple
>> times and do not run "make clean" before re-running "make"
>
> To avoid this needs very careful source layout (Makefile.am mainly).
AFAIK, we have such a layout. I rarely run into these errors (have not
for some time now) -- this is mainly based on anecdotal experiences
from a long time ago (probably with prior versions of AM) and where I
did not do a complete analysis of what the exact problem was. In most
(all?) cases, a "make clean all" fixed things, however.
>> - Solaris' dependency analysis gets mucked up upon successive
>> invocations of "make"
>
> This sounds like a bug in `depcomp'. Care to write a bugreport against
> Automake?
Not to worry -- I'm not shy there (I have submitted a bug or two
against AM). This is anecdotal recollections, however, so I have
nowhere near the appropriate data for a proper bug report.
Another important thing to check (sorry -- should have thought of this
the first time I posted) is that if you're building on an NFS-mounted
filesystem, ensure that the time on your client machine is tightly
synchronized with that of your NFS server (e.g., with ntp).
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
