Re: [Boost-build] Only -mt libs being built!

From: Neal Becker (ndbecker2_at_[hidden])
Date: 2008-04-09 13:25:05

Jurko Gospodnetić wrote:

>    Hi Neal.
> 
>> Thanks, but now I get this
>> 
>> bjam -sICU_PATH=/usr -sEXPAT_INCLUDE=/usr -sEXPAT_LIBPATH=/usr/lib64
>> --layout=system --build-type=complete stage
>> 
>> warning: skipping optional Message Passing Interface (MPI) library.
>> note: to enable MPI support, add "using mpi ;" to user-config.jam.
>> note: to suppress this message, pass "--without-mpi" to bjam.
>> note: otherwise, you can safely ignore this message.
>> Building Boost.Regex with Unicode/ICU support enabled
>> Using ICU in /usr/include
>> warning: No toolsets are configured.
>> warning: Configuring default toolset "gcc".
>> warning: If the default is wrong, your build may not work correctly.
>> warning: Use the "--toolset=xxxxx" option to override our guess.
>> warning: For more configuration options, please consult
>> warning:
>> http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html
>> ...
> 
>    Hmmm, just a hunch, but could you try specifying the gcc toolset
> explicitly? Just add 'toolset=gcc' to the command line (do not specify
> just 'gcc' but specify the 'toolset=' prefix as well).
> 
>    Hope this helps...
> 

Nope, same result:

bjam -sICU_PATH=/usr -sEXPAT_INCLUDE=/usr -sEXPAT_LIBPATH=/usr/lib64 --layout=system --build-type=complete
toolset=gcc stage 
(also tried
bjam -sICU_PATH=/usr -sEXPAT_INCLUDE=/usr -sEXPAT_LIBPATH=/usr/lib64 --layout=system --build-type=complete --toolset=gcc
stage)