Subject: Re: [Boost-build] bjam install
From: Belcourt, K. Noel (kbelco_at_[hidden])
Date: 2010-11-19 21:54:23
On Nov 19, 2010, at 7:30 PM, Bryce Lelbach wrote:
> I let one of the processes run in an idle shell, just for kicks.
> Eventually, it
> did finish, but, clearly there's a problem if three copy commands
> and a ln-UNIX,
> are taking 5+ minutes... is this likely an issue on my end?
No I don't think so.
> wash_at_Pegasus:~/boost$ time bjam install --prefix=/usr/local/
I suspect this is the well known bjam startup penalty. If I
understand it correctly, it amounts to the overhead involved in
recreating the dependency graph and determining out of date targets
each time bjam starts up (about 5 minutes on a slower system, around
90 seconds on a faster one).
One way to test this is to cd to boost/status, edit the Jamfile to
remove all libraries/test except for (in your case) system/test, and
rerun bjam, does it still take 5+ minutes before patience ends and
targets start building?
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