Re: [boost] Re: [1.32] SunPRO build failures

From: Aleksey Gurtovoy (agurtovoy_at_[hidden])
Date: 2004-12-02 06:01:44

Caleb Epstein writes:
> On Wed, 01 Dec 2004 14:53:19 -0600, Rene Rivera
> <grafik.list_at_[hidden]> wrote:
> > > Aleksey: how do I get the compiler version information to show up as
> > > part of the toolset name in the regression results (e.g.
> > > gcc-3.3.4-sunos5 instead of just gcc)?
> > 
> > Add a toolset as boost-root/tools/build/v1/gcc-3_3_4-sunos5.jam with:
> > 
> > {
> >      extends gcc ;
> > }
> 
> Thanks.  I was hoping this might be handled automatically somehow, 

Hopefully when we switch over to Boost.Build v2.

> so I don't need to patch my Boost tarball or change anything when I 
> upgrade gcc versions.

We could provide a way to alias a toolset in 'regression.py', but as soon 
as you'd want to start testing with two or more different gcc versions 
you'd _have_ to have a differently named toolset anyway, so basically it's 
not worth it.

Patching is easy, though: just put an executable script named 
'patch_boost' that does what you want in the same directory with 
'regression.py' and it would be automatically picked up and executed
before the actual tests are started.

--
Aleksey Gurtovoy
MetaCommunications Engineering