From: Sheppard, Mark (Mark.Sheppard_at_[hidden])
Date: 2008-05-14 07:42:53
Sheppard, Mark wrote:
> Vladimir Prus wrote:
>> On Wednesday 30 April 2008 15:11:55 Sheppard, Mark wrote:
>>> However I'd have thought that if the problem was just in our Jambase
>>> and Jamfiles then there should be some error produced by jam rather
>>> than it exiting early with a zero exit status. To my mind this
>>> indicates that there might be a problem in jam itself. Has anyone
>>> else seen similar behaviour to this?
>> I suspect you might either have to produce a self-contained example,
>> or debug this yourself, like by adding prints in make*.c that explain
>> in more detail what happens with the file that is not rebuilt.
> Yes, I thought that would be the case :-(. I'll keep digging.....
I did keep digging for quite a while, but didn't manage to get to the
bottom of it. In the end I worked round the problem by adding code to
compare the value of counts->updating in make.c with the value of
counts->made in make1.c, and if there's an underbuild then spawn jam
again with the same arguments. It's pretty nasty, but it works.
Sorry I didn't have the time to fix this properly :-(.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk