How to force bjam to build but don't to run boost regression test suite?

I need to build boost regression test suite on a build machine (linux) and then run on a SUT (target machine, linux). The necessary boost libraries are already installed on the SUT as shared ones. I have properly installed gcc toolchain on the build machine. The SUT has no gcc at all.

I have built bjam on the build machine as native utility. Then I have cross-compiled some useful utility (process_jam_log and library_status) as described here: http://ift.tt/1OsruGD

The main idea is to build (cross-compile) overall regression test suite on the build machine, then to copy to the SUT and finally to run on the latter. But when bjam builds some test it tries to run the test immediately on the build machine in the native environment.

Decisions from boost.org I have found (e.g. http://ift.tt/1Osrxly) suppose that someone wants to build and run the test suite on the machine boost libraries already installed on. It seems my case doesn't mentioned in google.

My question is how to force bjam to miss the run stage? Or how to reach my intention elsewhere?