Firstly I’m new to this, I apologize in advance if I’m supposed to wait until I’m a subscribed member before posting, or if this is even the correct way to say this.

 

I’m use Boost.Jam 3.1.16

To build Boost 1.36.0

 

I think my problem can be summed up with three pastes:

 

vvvvvvvvvvvv

D:\boost_3_1_16>bjam --toolset=msvc stage

###

### No toolset specified. Please use --toolset option.

###

### Known toolsets are: acc, borland, cc, como, darwin, gcc, gcc-nocygwin, intel

-linux, intel-win32, kcc, kylix, metrowerks, mingw, mipspro, msvc, qcc, pathscal

e, pgi, sun, sunpro, tru64cxx, vacpp, vc7, vc8, vc9, vmsdecc

###

^^^^^^^^^^^

 

The outcome is the same if I omit the toolset parameter.  So I noticed that vc9 is clearly an option for toolset, so I tried this:

 

vvvvvvvvvvv

D:\boost_3_1_16 >bjam --toolset=vc9 stage

vc9.jam: No such file or directory

D:/include/tools/build/v2/build\toolset.jam:38: in toolset.using

rule vc9.init unknown in module toolset.

D:/include/tools/build/v2\build-system.jam:434: in process-explicit-toolset-requ

ests

D:/include/tools/build/v2\build-system.jam:513: in load

D:\include\tools\build\v2/kernel\modules.jam:281: in import

D:\include\tools\build\v2/kernel/bootstrap.jam:128: in boost-build

D:\include\boost-build.jam:16: in module scope

^^^^^^^^^^

 

Now, you might be thinking “well vc9 was there for decoration, and msvc is really what you want, and perhaps your environment is messed up?” But behold what happens when I do a build for jam.

 

vvvvvvvvvv

D:\bjam_1_36_0 >build

Setting environment for using Microsoft Visual Studio 2008 x86 tools.

###

### Using 'vc9' toolset.

###

(… continues to build properly…)

^^^^^^^^^^

 

So build.bat in bjam works flawlessly to autodetect and use one of my compilers.  So if my environment were messed up why does bjam build properly with auto-detection? (btw, I tried autodetection too)

 

So, it appears as though bjam is just mysteriously broken.  User-config.jam didn’t seem useful to me.

 

-          Max