Richard I have found the following to work for me. I have several versions of the compiler installed on my system for different projects. I also have several versions of python installed too. in my user-config.jam file in my home directory I have the following entries: using gcc : : /usr/local/gcc-4.1.2/bin/g++ : <linkflags>"-Wl,-rpath -Wl,/usr/local/gcc-4.1.2/lib" ; and using python : 2.5 : /usr/local/python-2.5.1_gcc-4.1.2 ; then I use the following command to build a version of boost. bjam --without-wave --without-test --prefix=<where to install to> --includedir=<where to put headers> --toolset=gcc stage NOTE: I am running on Linux. HTH Dave Riedel Richard Hadsell wrote:
Options for building the Boost libraries with bjam seem to have changed from 1.33 to 1.34. At least, I can't be sure that the result will be the same. I looked at the 1.34.0 beta docs and the common.jam and gcc.jam files, but I am still unsure of what to do.
I built the 1.33.x libraries this way:
setenv PYTHON_VERSION 2.3 bjam -sTOOLS=gcc -sGCC_ROOT_DIRECTORY=/opt/gcc344 -sGXX="g++344 -m64" -sGCC="gcc344 -m64" --with-python-root=/usr --stagedir=stageFC3 -sBUILD="debug release <threading>multi <shared-linkable>true <instruction-set>opteron" stage
Most of the options make it obvious what I want. The '<shared-linkable>true' option was necessary to add '-fPIC', which our binaries need in order to dynamically link (plug-in) shared libraries.
I will appreciate any help you can offer in making the transition to 1.34.0 easier.
BTW, it would be nice to see a list of available options for each toolset that comes with Boost bjam.