John Maddock
This indicates that the Microsoft native include is specified BEFORE the STLPort one. This would explain why the config_info doesn't reflect the STLPort usage.
Can someone tell me what I should be doing differently?
I don't know, but the dmc toolset is broken for the same reason. Actually this seems to me to be a bad design decision: why would the compilers include directory be present on the command line at all? If my compilers environment has been modified to place some other directory first (for example in vcvars32.bat) then why would bjam subvert that? I traced this to changes made at the beginning of august by Rene Rivera to factor out commonalities of stlport toolset. Basically not a bad idea but it ended up with this error. Rene is the best person to fix it if he's around. I sent him a private email but go no response. So I'm a little bit in holding pattern on this. Apparently there are some loose ends with the stlport/serialization library combination that I would like to resolve. Robert Ramey