[Boost-testing] [LOG] parses toolset incorrectly (was: Re: Change to toolset configuration on trunk)

Subject: [Boost-testing] [LOG] parses toolset incorrectly (was: Re: Change to toolset configuration on trunk)
From: Ben Pope (benpope81_at_[hidden])
Date: 2013-05-14 23:33:24

On 15/05/13 11:04, Ben Pope wrote:
> On 14/05/13 22:16, Rene Rivera wrote:
>> On Tue, May 14, 2013 at 12:46 AM, Ben Pope <benpope81_at_[hidden]
>> <mailto:benpope81_at_[hidden]>> wrote:
>>
>>     It appears something has changed on trunk as my test runner stopped
>>     working (on trunk, release is still fine) around the 5th May, I
>>     suspect I was doing something wrong.
>>
>>     user-config.jam contains:
>>
>>     using gcc : 4.8.0_c++11 : g++-4.8 : <cxxflags>-std=c++11 ;
>>
>>     Invocation of run.py:
>>     ./run.py --tag=trunk --runner="BP x86_64 C++11"
>>     --toolsets=gcc-4.8.0_c++11,__clang-3.2_c++11_libc++
>> --bjam-options=-j7
>>
>>     bjam.log outputs:
>>
>> /home/ben/development/boost/__test/build/tools_bb/util/__numbers.jam:22:
>>     in numbers.check from module numbers
>>     error: 0_c++11 in 4 8 0_c++11
>>     error: is not a number
>>
>>     Fair enough, seems I was abusing the version field (for both clang
>>     and gcc)
>>
>>     Is there a recommended way of creating a toolset with a name that
>>     has certain options defaulted, such as std=c++11?
>>
>>
>> Try using the tilde ("~") as a separator between the numerical version
>> number and the rest of the toolset name.
>
> Hmm, no go:
>
> using gcc : 4.8.0~c++11 : g++-4.8 : <cxxflags>-std=c++11 ;
>
>
> error: 0~c++11 in 4 8 0~c++11
> error: is not a number
>
> I suspect this affects marshall-mac runners as well, but the tilde seems
> to work for VeecoFTC with msvc-9.0~w.

I guess I should have pasted more context:

/home/ben/development/boost/test/build/tools_bb/build/version.jam:70: in 
version.version-less from module version
../libs/log/build/Jamfile.v2:178: in 
Jamfile</home/ben/development/boost/test/build/boost/libs/log/build>.ssse3-targets-cond 
from module 
Jamfile</home/ben/development/boost/test/build/boost/libs/log/build>
/home/ben/development/boost/test/build/tools_bb/kernel/modules.jam:107: 
in modules.call-in from module 
Jamfile</home/ben/development/boost/test/build/boost/libs/log/build>

So Log is attempting to check the toolset version to add target specific 
compilation flags.

I can't really tell what's going on, but is Log replacing my cxxflags? 
Is it impossible for me to decide which cxxflags I want to compile Log with?

Ben