Boost logo

Boost Testing :

Subject: Re: [Boost-testing] [1.41.0] Release testing
From: Belcourt, Kenneth (kbelco_at_[hidden])
Date: 2009-09-14 16:00:46


Hi Volodya,

On Sep 12, 2009, at 12:11 AM, Vladimir Prus wrote:

> Beman Dawes wrote:
>
>> On Fri, Sep 11, 2009 at 12:34 PM, Belcourt, Kenneth <kbelco_at_[hidden]
>> > wrote:
>>> Hi Beman,
>>>
>>> On Sep 10, 2009, at 5:07 AM, Beman Dawes wrote:
>>>
>>>> On Thu, Sep 10, 2009 at 12:42 AM, Steve M.
>>>> Robbins<steve_at_[hidden]> wrote:
>>>>>
>>>>> On Fri, Sep 04, 2009 at 10:27:18AM -0400, Beman Dawes wrote:
>>>>>>
>>>>>> On Thu, Sep 3, 2009 at 11:02 PM, Steve M.
>>>>>> Robbins<steve_at_[hidden]>
>>>>>> wrote:
>>>>>>>
>>>>>>> On Thu, Sep 03, 2009 at 07:36:43AM -0400, Beman Dawes wrote:
>>>>>>>>
>>>>>>>> Release testing is running smoothly, so I'd like volunteers
>>>>>>>> to start
>>>>>>>> release testing some additional compilers:
>>>>>>>>
>>>>>>>> * Most recent GCC 4.4.x compiler, with C++0x features enabled.
>>>>>>>
>>>>>>> I can do that on linux.
>>>>>>
>>>>>> Good. I assume this will be the "Debian-Sid" tester?
>>>>>
>>>>> Yes. I finally figured out how to configure this, and the
>>>>> reports are
>>>>> up now. However, I haven't figured out how to suffix the name
>>>>> with
>>>>> "c++0x" as you had suggested previously.
>>>>
>>>> Perhaps Noel could explain how he does it:-?
>>>
>>> Sure. I'm on travel so my responses will be slow to non-existent.
>>>
>>> // user-config.jam
>>>
>>> using gcc
>>> : 4.4.1
>>> : /home/sntools/extras/compilers/gcc-4.4.1/bin/g++
>>> ;
>>>
>>> using gcc
>>> : 4.4.1-0x
>>> : /home/sntools/extras/compilers/gcc-4.4.1/bin/g++
>>> : <cxxflags>-std=gnu++0x
>>> ;
>>>
>>> but Boost.Build has a problem with using a dash as a toolset version
>>> separator, Boost.Build seems to think it's a sub-feature. So I
>>> patched
>>> feature.jam and use the patch_boost script to copy the patched
>>> feature.jam
>>> into boost/tools/build/v2/build/feature.jam.
>>
>> Thanks for the info. I'll let Volodya comment on the need to patch
>> feature.jam:-)
>
> I was under impression that such a patch was committed months ago. I
> surely
> did port something very much like it to Python branch of Boost.Build
> last
> weekend. I'll double-check later today.

I'm getting this error when using this user-config.jam to run the
trunk tests.

// user-config.jam
using gcc
   : 4.3.3-0x
   : /home/sntools/extras/compilers/gcc-4.3.3/bin/g++
   : <cxxflags>-std=gnu++0x
   ;

notice: will use '/home/sntools/extras/compilers/gcc-4.3.3/bin/g++'
for gcc, condition <toolset>gcc-4.3.3-0x
/var/scratch/boost/tools_bb/build/feature.jam:307: in implied-
subfeature from module feature
error: "0x" is not a known subfeature value of <toolset>gcc
/var/scratch/boost/tools_bb/build/feature.jam:489: in feature.validate-
value-string from module feature
/var/scratch/boost/tools_bb/build/property.jam:276: in validate1 from
module property
/var/scratch/boost/tools_bb/build/property.jam:301: in validate from
module property
/var/scratch/boost/tools_bb/build/property.jam:310: in
property.validate-property-sets from module property
/var/scratch/boost/tools_bb/build/toolset.jam:151: in toolset.flags
from module toolset
/var/scratch/boost/tools_bb/tools/common.jam:430: in common.handle-
options from module common
/var/scratch/boost/tools_bb/tools/gcc.jam:137: in gcc.init from module
gcc
/var/scratch/boost/tools_bb/build/toolset.jam:38: in using from module
toolset
/var/scratch/boost/tools_bb/user-config.jam:51: in modules.load from
module user-config
/var/scratch/boost/tools_bb/build-system.jam:241: in load-config from
module build-system
/var/scratch/boost/tools_bb/build-system.jam:383: in load-
configuration-files from module build-system
/var/scratch/boost/tools_bb/build-system.jam:538: in load from module
build-system
/var/scratch/boost/tools_bb/kernel/modules.jam:283: in import from
module modules
/var/scratch/boost/tools_bb/kernel/bootstrap.jam:142: in boost-build
from module
/var/scratch/boost/boost-build.jam:17: in module scope from module

I'll leave the Sandia-gcc trunk tests setup to use -0x so if you
commit a patch to fix this, you should see the next test cycle start
reporting results.

- Noel

Here's the nightly cron daemon script




Boost-testing list run by mbergal at meta-comm.com