From: David Abrahams (dave_at_[hidden])
Date: 2008-08-06 11:37:28
on Sat Aug 02 2008, Michael Rogers <m.rogers-AT-hef.ru.nl> wrote:
> This link pretty much describes what is happening to me.
> Does anyone else experience this? Anyone know how to fix it?
Looks like a bug in either Darwin's linker (hangs) or in its
implementation of execwait. bjam is just waiting for the linker process
My suggestion, to find out which: run bjam again with -n -a (build
nothing) or -d+2 (rebuild what's out of date) and look at the linker
command that bjam is issuing. Then try it yourself from a shell
prompt. If it hangs, you know it's the linker. If not, it's either a
bug in execwait or a bug in the way bjam is using it.
-- Dave Abrahams BoostPro Computing http://www.boostpro.com
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