-bash-3.00# ./bjam -sTOOLS=gcc --without-python --with-thread "-d+2"
...
set -e
"g++" -c -Wall -ftemplate-depth-255 -DNDEBUG -DNDEBUG -DBOOST_THREAD_LIB_NAME=boost_thread -DBOOST_THREAD_BUILD_DLL=1 -O3 -finline-functions -Wno-inline -pthread -fPIC -I"bin/boost/libs/thread/build" -I "/home/quantum/boost_1_33_1" -o "bin/boost/libs/thread/build/libboost_thread.so/gcc/release/shared-linkable-true/threading-multi/exceptions.o" "/home/quantum/boost_1_33_1/libs/thread/build/../src/exceptions.cpp"
I've only snipped the error messages, but g++ is not my compiler. I've set CXX=i386-unknown-openbsd3.8-eg++, 'cause that's what its named on OpenBSD when you build a compiler from ports.
Quantum Skyline wrote:
> I guess I'm screwed then, eh? :)
>
> Is it possible to get Boost.Jam or the compile process to dump which version
> of GCC its using on my system?
If you execute bjam directly, instead of from the Makefile, you can pass
it a "-d+2" option which prints out all the commands it executes. And
yes, running it through the Makefile is likely using the default system
compiler.
--
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
_______________________________________________
Boost-users mailing list
Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users