Running bjam in boost/tools/build/v2/test doesn't (seem to) run build's regressions. Instead, I get: jamfile.jam:8: in modules.load rule project-root unknown in module Jamfile</F:/tmp/boost-MinGW-32/trunk/boost/t ools/build/v2/test>. F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2/build\project.jam:314: in load- jamfile F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2/build\project.jam:62: in load F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2/build\project.jam:168: in proje ct.find F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2\build-system.jam:569: in load F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\..\kernel\modules.jam:283: in import F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\..\kernel\bootstrap.jam:14 2: in boost-build F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\boost-build.jam:14: in mod ule scope If I run "python absolute_sources.py" (to pick that test as an example), I get very little (and it doesn't match regression test output): F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\TestCmd.py:60: Deprecation Warning: The popen2 module is deprecated. Use the subprocess module. import popen2 Am I close? I realize that build is a different animal. Are there instructions for running its tests in isolation? (Could those instructions be put in boost/tools/build/v2/index.html?)