id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
119	auto-configuration unreliable	ghost	Dave Abrahams	"Martin reports that auto-configuration does not work nice for him. His user-config.jam is:
{{{
using python : 2.4 : /usr : : ;

using gcc : 3.4.6_linux_x86_64 : /usr/local/gcc-3.4.6/bin/g++wrap 
--limit-memory=900 --limit-cpu=1800 : <compileflags>""-D_GLIBCXX_DEBUG=1"" 
<root>/usr/local/gcc-3.4.6
;

using gcc : 3.4.5_linux_x86_64 : /usr/local/gcc-3.4.5/bin/g++wrap 
--limit-memory=900 --limit-cpu=1800 : <compileflags>""-D_GLIBCXX_DEBUG=1"" 
<root>/usr/local/gcc-3.4.5
;

using gcc : 4.1.0_linux_x86_64 : /usr/local/gcc-4.1.0/bin/g++wrap 
--limit-memory=900 --limit-cpu=1800 : <compileflags>""-D_GLIBCXX_DEBUG=1"" 
<root>/usr/local/gcc-4.1.0
;

using python : 2.4 : /usr/local/python/2.4/gcc-4.1.0 : : : <toolset>gcc 
<toolset-gcc:version>4.1.0_linux_x86_64 ;
}}}

and when bjam is run as:
{{{
(""/b/r/rc/boost/tools/jam/src/bin.linux/bjam"" --v2 
""-sBOOST_BUILD_PATH=/b/r/rc"" 
""-sBOOST_ROOT=/b/r/rc/boost"" 
""--toolset=gcc-3.4.5_linux_x86_64"" 
-d2 --dump-tests  ""--build-dir=/b/r/rc/results"" >>""/b/r/rc/results/bjam.log"" 2>&1).
}}}

Boost.Build seem to use gcc-3.4.6 -- which is the version that plain 'gcc' refers too. 

While we're at it, it's not clear if ""toolset="" as opposed to ""--tooset="" should cause auto-configuration to happen."	defect	closed	major	C++ Boost maintenance	component1		fixed