[Boost-build] Jam newer bug on OSX

From: Salvatore Domenick Desiano (sal_at_[hidden])
Date: 2007-02-28 21:02:17

I seem to have run into a bug in timestamp checking on OSX. It's pretty 
simple to reproduce:

Jamfile
--------
Library libtest : object.c ;

object.c
---------
void object_function () { }

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.

I don't know if it's related, but I've also noticed that jam doesn't run 
ranlib on OSX. Is this by design or a bug?

I know it's not useful to say a problem is urgent, but I'm facing a 
constant rebuild of every file in my project, so even a cheap hack 
workaround would be welcome.

Thank you!

-- Sal
smile.

--------------
   Salvatore Domenick Desiano
     Doctoral Candidate
       Robotics Institute
         Carnegie Mellon University