[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Spurious rebuilds
From: |
craig . howard |
Subject: |
Re: Spurious rebuilds |
Date: |
Sun, 4 May 2003 16:15:36 -0700 |
User-agent: |
KMail/1.5.9 |
On May 4, 2003 03:11 pm, Alexandre Duret-Lutz wrote:
> >>> "craig" == craig howard <address@hidden> writes:
>
> craig> I'm having trouble with spurious rebuilds caused by
> craig> autoconf/automake projects. This problem is _not_
> craig> happening with handmade makefiles. What's happening is
> craig> that everytime I execute make, the entire project is
> craig> rebuilt, regardless of whether or not each file needs to
> craig> be.
>
> craig> I was able to duplicate the problem with a skeleton project of the
> craig> following
>
> This works fine for me (using autoconf 2.57 and automake 1.7.4,
> but that shouldn't matter).
>
> craig> Is there something simple that I've misconfigured? I
> craig> doubt it's a problem with the configure.in or
> craig> Makefile.am files, as I have the same issue with KDE
> craig> CVS.
>
> A wild guess: are you compiling these things in an NFS mounted
> directory? Weird timestamp issues are often caused by NFS
> clients which aren't date-synchronized with NFS servers.
>
> [...]
Yes, thanks. I resolved this issue. Somehow the timestamps on my system
files were set to the year 2024. I have no idea how it happened (it is a
local filesystem), but touching all files with the incorrect timestamp
worked.
I blamed the project on autoconf/automake because the one
non-autoconf/automake project I tried didn't include any system headers. Go
figure, eh?
Thanks for the response.
--
Craig Howard
3B Computer Science -- University of Waterloo
address@hidden