|
Boost-Build : |
Subject: Re: [Boost-build] Cannot get b2 to use crayc++
From: Ilja Honkonen (ilja.honkonen_at_[hidden])
Date: 2012-11-15 03:10:20
>>> bjam toolset=cray
>>> Add -d2 to display debug information if this doesn't work.
>> Thanks. It seems multiple using lines in the .jam file is also supported
>> so requiring the toolset command line argument makes sense.
> The first toolset that you initialize should be the
> default. If this is the only using statement and
> you have to specify the toolset on the command line,
> then it's a bug.
I have to specify the toolset even if there is only one using line in
user-config.jam:
tar xf boost_1_52_0.tar.bz2
cd boost_1_52_0/
./bootstrap.sh
echo "using cray : 8.1.1 : CC ;" >> ./tools/build/v2/user-config.jam
./b2 --with-test -d2
prints:
Building the Boost C++ Libraries.
Component configuration:
- chrono : not building
- context : not building
- date_time : not building
- exception : not building
- filesystem : not building
- graph : not building
- graph_parallel : not building
- iostreams : not building
- locale : not building
- math : not building
- mpi : not building
- program_options : not building
- python : not building
- random : not building
- regex : not building
- serialization : not building
- signals : not building
- system : not building
- test : building
- thread : not building
- timer : not building
- wave : not building
...patience...
...found 985 targets...
...updating 65 targets...
common.mkdir bin.v2
mkdir -p "bin.v2"
common.mkdir bin.v2/libs
mkdir -p "bin.v2/libs"
common.mkdir bin.v2/libs/test
mkdir -p "bin.v2/libs/test"
common.mkdir bin.v2/libs/test/build
mkdir -p "bin.v2/libs/test/build"
common.mkdir bin.v2/libs/test/build/gcc-4.3
mkdir -p "bin.v2/libs/test/build/gcc-4.3"
common.mkdir bin.v2/libs/test/build/gcc-4.3/release
mkdir -p "bin.v2/libs/test/build/gcc-4.3/release"
common.mkdir bin.v2/libs/test/build/gcc-4.3/release/link-static
mkdir -p "bin.v2/libs/test/build/gcc-4.3/release/link-static"
common.mkdir
bin.v2/libs/test/build/gcc-4.3/release/link-static/threading-multi
mkdir -p
"bin.v2/libs/test/build/gcc-4.3/release/link-static/threading-multi"
gcc.compile.c++
bin.v2/libs/test/build/gcc-4.3/release/link-static/threading-multi/compiler_log_formatter.o
"g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline
-Wall -pedantic -pthread -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -c -o
"bin.v2/libs/test/build/gcc-4.3/release/link-static/threading-multi/compiler_log_formatter.o"
"libs/test/src/compiler_log_formatter.cpp"
...
./b2 --with-test -d2 toolset=cray prints:
...
- system : not building
- test : building
- thread : not building
- timer : not building
- wave : not building
...patience...
...found 982 targets...
...updating 58 targets...
common.mkdir bin.v2/libs/test/build/cray-8.1.1
mkdir -p "bin.v2/libs/test/build/cray-8.1.1"
common.mkdir bin.v2/libs/test/build/cray-8.1.1/release
mkdir -p "bin.v2/libs/test/build/cray-8.1.1/release"
common.mkdir bin.v2/libs/test/build/cray-8.1.1/release/threading-multi
mkdir -p
"bin.v2/libs/test/build/cray-8.1.1/release/threading-multi"
cray.compile.c++
bin.v2/libs/test/build/cray-8.1.1/release/threading-multi/execution_monitor.o
CC -c -h gnu -O3 -DBOOST_ALL_NO_LIB=1 -DBOOST_TEST_DYN_LINK=1
-DNDEBUG -I"." -o
"bin.v2/libs/test/build/cray-8.1.1/release/threading-multi/execution_monitor.o"
"libs/test/src/execution_monitor.cpp"
If I change the using line to gcc : 4.7.2 : CC then it works without
specifying the toolset. Both using intel : 13.0.0 : CC ; and using pgi :
12.9 : CC ; also try to use gcc if I don't specify the toolset. Compiler
versions are:
pgCC 12.9-0 64-bit target on x86-64 Linux -tp istanbul
Copyright 1989-2000, The Portland Group, Inc. All Rights Reserved.
Copyright 2000-2012, STMicroelectronics, Inc. All Rights Reserved.
Intel(R) C++ Intel(R) 64 Compiler XE for applications running on
Intel(R) 64, Version 13.0.0.079 Build 20120731
Copyright (C) 1985-2012 Intel Corporation. All rights reserved.
Cray C++ : Version 8.1.1 Thu Nov 15, 2012 09:08:24
Ilja
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk