Steven Watanabe Via Boost wrote:
I localized the problematic change in Boost.Compute: https://github.com/boostorg/compute/pull/689/files
If you want to reproduce it checkout master and develop branches of Boost.Compute and try to run the tests from BOOST_ROOT/status passing --dump-tests: cd status b2 --dump-tests
You should see lists of tests and with develop some number of tests are missing (from Detail, Geometry, Hash, Math, Multiprecision, Odeint, Parameter), also one entry from Config: boost-test(RUN) "config/link_test_test" : "libs/config/test/link/main.cpp"
I'm not sure how this should be fixed, besides commenting out lines in Compute's Jamfile, so I'm unable to create a PR. Changing 'compile' to use an 'obj' target instead should fix it. There's a bug with --dump-tests when a test target is used in a configure check. (Note that since
On 03/29/2017 01:00 PM, Adam Wulkiewicz via Boost wrote: this test probably shouldn't be reported in the regression output, using compile is not correct in the first place.)
To make sure I understand you correctly are you suggesting replacing `compile` rule with `exe` rule? So change: compile check/has_opencl.cpp : : has_opencl ; into exe has_opencl : check/has_opencl.cpp ; which works, btw. Adam