[Boost-build] [build] Problems building release branch

Subject: [Boost-build] [build] Problems building release branch
From: Jeremiah Willcock (jewillco_at_[hidden])
Date: 2010-10-04 14:20:42

When I run:

./bootstrap.sh
./bjam libs/graph/test/

in a fresh checkout of the release branch, I get the error:

THREAD JAMFILE libs/thread/build/Jamfile.v2 34 
Jamfile</dev/shm/release/libs/thread/build>. modules.load 
/dev/shm/release/tools/build/v2/build/project.jam 310 project. 
load-jamfile /dev/shm/release/tools/build/v2/build/project.jam 62 project. 
project.load /dev/shm/release/tools/build/v2/build/project.jam 760 
project. project.use /dev/shm/release/tools/build/v2/build/project.jam 89 
project. load-used-projects 
/dev/shm/release/tools/build/v2/build/project.jam 73 project. load 
/dev/shm/release/tools/build/v2/build/project.jam 168 project. 
project.find /dev/shm/release/tools/build/v2/build-system.jam 569 
build-system. load /dev/shm/release/tools/build/v2/kernel/modules.jam 283 
modules. import /dev/shm/release/tools/build/v2/kernel/bootstrap.jam 142 
boost-build /dev/shm/release/boost-build.jam 17  module scope
Performing configuration checks

     - has_icu builds           : yes
/dev/shm/release/tools/build/v2/build/feature.jam:485: in 
validate-value-string from module feature
error: "msvc:<linkflags>delayimp.lib" is not a known value of feature 
<toolset>
error: legal values: "gcc"
/dev/shm/release/tools/build/v2/build/feature.jam:358: in 
expand-subfeatures-aux from module feature
/dev/shm/release/tools/build/v2/build/feature.jam:419: in 
expand-subfeatures from module feature
/dev/shm/release/tools/build/v2/build/feature.jam:851: in feature.expand 
from module feature
/dev/shm/release/tools/build/v2/build/targets.jam:1027: in 
targets.evaluate-requirements from module targets
/dev/shm/release/tools/build/v2/build/targets.jam:1393: in 
basic-target.compute-usage-requirements from module 
object(alias-target-class)@420
/dev/shm/release/tools/build/v2/build/alias.jam:47: in 
compute-usage-requirements from module object(alias-target-class)@420
/dev/shm/release/tools/build/v2/build/targets.jam:1319: in 
object(alias-target-class)@420.generate from module 
object(alias-target-class)@420
/dev/shm/release/tools/build/v2/build/targets.jam:732: in generate-really 
from module object(main-target)@1616
/dev/shm/release/tools/build/v2/build/targets.jam:704: in 
object(main-target)@1616.generate from module object(main-target)@1616
/dev/shm/release/tools/build/v2/build/targets.jam:848: in 
targets.generate-from-reference from module targets
/dev/shm/release/tools/build/v2/build/targets.jam:1217: in 
generate-dependencies from module object(typed-target)@423
/dev/shm/release/tools/build/v2/build/targets.jam:1268: in 
object(typed-target)@423.generate from module object(typed-target)@423
/dev/shm/release/tools/build/v2/build/targets.jam:732: in generate-really 
from module object(main-target)@1617
/dev/shm/release/tools/build/v2/build/targets.jam:704: in 
object(main-target)@1617.generate from module object(main-target)@1617
/dev/shm/release/tools/build/v2/build/targets.jam:848: in 
targets.generate-from-reference from module targets
/dev/shm/release/tools/build/v2/build/targets.jam:1217: in 
generate-dependencies from module object(typed-target)@194
/dev/shm/release/tools/build/v2/build/targets.jam:1266: in 
object(typed-target)@194.generate from module object(typed-target)@194
/dev/shm/release/tools/build/v2/build/targets.jam:732: in generate-really 
from module object(main-target)@1598
/dev/shm/release/tools/build/v2/build/targets.jam:704: in 
object(main-target)@1598.generate from module object(main-target)@1598
/dev/shm/release/tools/build/v2/build/targets.jam:848: in 
targets.generate-from-reference from module targets
/dev/shm/release/tools/build/v2/build/targets.jam:1217: in 
generate-dependencies from module object(typed-target)@787
/dev/shm/release/tools/build/v2/build/targets.jam:1268: in 
object(typed-target)@787.generate from module object(typed-target)@787
/dev/shm/release/tools/build/v2/build/targets.jam:732: in generate-really 
from module object(main-target)@924
/dev/shm/release/tools/build/v2/build/targets.jam:704: in 
object(main-target)@924.generate from module object(main-target)@924
/dev/shm/release/tools/build/v2/build/targets.jam:848: in 
targets.generate-from-reference from module targets
/dev/shm/release/tools/build/v2/build/targets.jam:1217: in 
generate-dependencies from module object(alias-target-class)@872
/dev/shm/release/tools/build/v2/build/targets.jam:1268: in 
object(alias-target-class)@872.generate from module 
object(alias-target-class)@872
/dev/shm/release/tools/build/v2/build/targets.jam:732: in generate-really 
from module object(main-target)@953
/dev/shm/release/tools/build/v2/build/targets.jam:704: in 
object(main-target)@953.generate from module object(main-target)@953
/dev/shm/release/tools/build/v2/build/targets.jam:258: in 
object(project-target)@631.generate from module object(project-target)@631
/dev/shm/release/tools/build/v2/build-system.jam:735: in load from module 
build-system
/dev/shm/release/tools/build/v2/kernel/modules.jam:283: in import from 
module modules
/dev/shm/release/tools/build/v2/kernel/bootstrap.jam:142: in boost-build 
from module
/dev/shm/release/boost-build.jam:17: in module scope from module

Is this a known problem?  Is there a quick workaround for me to use 
locally?  I just need this tree to test changes being merged over from the 
trunk.

-- Jeremiah Willcock