Re: [Boost-build] Mixing toolsets

Subject: Re: [Boost-build] Mixing toolsets
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2011-04-05 20:39:34

AMDG

On 03/30/2011 12:15 PM, Bo Jensen wrote:
> On Wed, Mar 30, 2011 at 7:06 PM, Steven Watanabe<watanabesj_at_[hidden]>  wrote:
>> On 03/30/2011 12:00 PM, Bo Jensen wrote:
>>>
>>> On Wed, Mar 30, 2011 at 6:37 PM, Steven Watanabe<watanabesj_at_[hidden]>
>>>   wrote:
>>>>
>>>> On 03/30/2011 11:24 AM, Bo Jensen wrote:
>>> But if gcc is not defined first then it fails :
>>>
>>> gcc.compile.c++
>>> bin/gcc/release/address-model-32/threading-multi/sulumnetc.o
>>> /bin/sh: -ftemplate-depth-128: not found
>>>
>>> Clearly the toolset is not set up properly and I am sure it's my
>>> fault, how should I set the toolset up in my user-config.jam ?
>>>
>>
>> using gcc : ... ;
>> using intel : ... ;
>>
>> doesn't just work, then it's probably a bug.
>> What exactly are the contents of your user-config.jam?
>
> Here it goes :
>
> # This is for new gcc-4.6.0
> using gcc : : :<compileflags>"-O3" ;
>
> # This is for intel 11
> using intel-linux : : :<compileflags>"-wd278 -wd279 -wd1292 -wd858
> -wd191 -wd981 -wd1628 -wd592 -wd1125 -gcc-name=gcc-4.2
> -gxx-name=g++-4.2" ;
>

So according to what you said above, this version
should work and if you switch gcc and intel-linux,
it no longer works?  If so I have a guess about
what's going on.

The intel-linux toolset inherits from the gcc toolset.
I suspect that registering intel-linux accidentally
registers a non-existent gcc version.  Since it
was declared before the gcc you explicitly define,
it becomes the default.

In Christ,
Steven Watanabe