From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-03-04 08:43:55
On Thursday 01 March 2007 05:02, Salvatore Domenick Desiano wrote:
> I seem to have run into a bug in timestamp checking on OSX. It's pretty
> simple to reproduce:
>
> Jamfile
> --------
> Library libtest : object.c ;
The 'Library' above makes me thing you're using
classic jam rules, not Boost.Build. Unfortunately,
those are completely unsupported.
> Every time you run jam, the object gets rebuilt and so does the archive.
> I've stepped through the jam code with gdb, and the problem appears to
> be in the time stamp check. That is, object.o gets a timestamp of 0
> (since it gets deleted after being archived) and object.c is always
> newer. This doesn't happen on SUSE, but I'm not sure what the difference
> is.
object.o should have TEMPORARY flag on it to prevent that. I have
no idea why behaviour on SUSE and OSX is different. But anyway,
unless you're using Boost.Build rules ("lib"), there's nothing we can do.
- Volodya