on Mon Apr 30 2007, Richard Hadsell
Richard Hadsell wrote:
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
I have made several attempts to persuade bjam to use /opt/gcc344/bin/g++344, and I finally discovered a solution for this part of the problem. I followed the Boost.Config doc
That won't help you. The ONLY thing that script does is set up some #defines that tell Boost about your compiler (mostly C++ standard conformance). John, people keep making this mistake; could you add a clarifying note to those docs? -- Dave Abrahams Boost Consulting http://www.boost-consulting.com Don't Miss BoostCon 2007! ==> http://www.boostcon.com