id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
142	Build config for gcc: GCC and GXX variables broken	reed	René Rivera	"{{{

I am on Linux (Red Hat 7.3) using GCC.

I have a CVS build of GCC installed in an unusual
directory, and I want to tell bjam to use that compiler.

So I ran 

./bjam -sGCC_ROOT_DIRECTORY=/lpr/wearables
-sGCC=gcc-3.3 -sGXX=g++-3.3 boost_thread

But bjam tries to use ""/lpr/wearables/bin/g++"" instead
of ""/lpr/wearables/bin/g++-3.3"", which is what I expected:

-----------------
    /lpr/wearables/bin//g++  -c -Wall
-ftemplate-depth-100  -DBOOST_THREAD_BUILD_DLL=1  -g
-O0 -fno-inline -pthread -fPIC   -I""libs/thread/build""
 -I ""/home/reed/boost_1_30_0""  -o
""libs/thread/build/bin/libboost_thread.so/gcc/debug/runtime-link-dynamic/shared-linkable-true/threading-multi/condition.o""
 ""libs/thread/build/../src/condition.cpp"" 

/bin/sh: /lpr/wearables/bin//g++: No such file or directory
...failed gcc-C++-action
libs/thread/build/bin/libboost_thread.so/gcc/debug/runtime-link-dynamic/shared-linkable-true/threading-multi/condition.o...
gcc-C++-action
libs/thread/build/bin/libboost_thread.so/gcc/debug/runtime-link-dynamic/shared-linkable-true/threading-multi/mutex.o
------------------

Even doing something silly like:

./bjam -sGXX=xlogo -sGCC=xlogo

causes bjam to use the default g++.

So I get the feeling that bjam is not honoring the GXX
or GCC variables (The documentation that led me to use
them is here:
http://www.boost.org/tools/build/gcc-tools.html)

Thanks

reed





}}}"	Bugs	closed		None	None		Fixed