One of the few options Boost users have for speeding up long compiles is to throw more machines at the problem, as with distcc (http://code.google.com/p/distcc/). I was just wondering why I couldn't get distcc's incredible "pump" mode to work as well as it should, and discovered this text: "In distcc-pump mode, the include server is unable to handle certain very complicated computed includes as found in parts of the Boost library. The include server will time out and distcc will revert to plain mode." (http://distcc.googlecode.com/svn/trunk/doc/web/man/distcc_1.html#TOC_22). It's nice that they consider it a bug, but it doesn't sound they're going to go out of their way to fix it. Just another lovely trade-off to keep in mind when making design decisions... ;-) -- Dave Abrahams BoostPro Computing http://www.boostpro.com