Regression test script refuses to use non-default toolset when user-config.jam is missing

[li51ckf02@…]

When executing python run.py --runner=blabla --toolsets=qcc on QNX 6.4.0 when there is no user-config.jam, you get this:
warning: No toolsets are configured.
warning: Configuring default toolset "gcc".

configure works as expected and detects the default toolset as qcc. Regression tests work after doing this.

[Steven Watanabe]

You need a user-config.jam in your home directory which should contain

using qcc ;

[viboes]

I don't know if there is an error in your command "qcc" or "gcc"? Can we close this ticket?

[li51ckf02@…]

Both qcc and gcc are valid toolsets on QNX.

What I don't understand is why the regression script overrides my choice. Why would the default toolset have a greater chance of working in the absence of user-config.jam? Why not just use the toolset I've told it to use?

I've changed the summary to more accurately reflect the issue. I'm assuming this isn't actually tied to QNX but I haven't verified that.

If this isn't fixed, at least the documentation at http://www.boost.org/development/running_regression_tests.html should be updated. For example with this additional step in the step by step instructions:

24. Create a user-config.jam file in your home directory that contains the toolset(s) you want to test with. You can use the Boost bootstrap script to generate it.

[Niklas Angare <li51ckf02@…>]

Trac didn't pick up my name on the last post. Trying again (sorry for the spam).

[Steven Watanabe]

The regression test script should probably pass toolset=qcc instead of qcc to bjam. This allows the toolset to be automatically initialized. There may also be issues with the Boost.Build tests.

[René Rivera]

The regression script has passed toolset= for some time now.