From: West, Larry (Larry_West_at_[hidden])
Date: 2007-06-20 23:04:48
> From: Vladimir Prus
>> This seems like it must be an error on my part, since it shows up on
>> first "make": bjam errors out immediately saying it can't find
> Can you try just "sun". In Boost.Build V2 that's how support module
> for Sun compiler is called -- after all sun only produces one
> and the branding is not obvious, so "sun" is the one part of the name
> we always can be sure of.
> - Volodya
Well, that's an interesting suggestion. The output from "configure
-n Building Boost.Jam with toolset sun...
./configure: ./bootstrap/jam0: not found
-n Detecting Python version...
-n Detecting Python root...
-n Unicode/ICU support for Boost.Regex?...
Generating Boost.Build configuration in user-config.jam...
And then "make" (Gnu make) yields:
/bin/sh: ./tools/jam/src//bjam: not found
Not all Boost libraries built properly.
My earlier ("sunpro") attempt had yielded a
"tools/jam/src/bin.solaris/bjam" executable, and the
"tools/jam/src//bjam" above makes me think that perhaps bjam itself
expects to be built --with-toolset=sunpro and the rest
And in fact, I did that: grabbed the bin.solaris/bjam from my sunpro
attempt, placed it in /usr/local/bin, and re-ran configure with the
additional flag "--with-bjam=/usr/local/bin/bjam" [as well as
"--with-toolset=sun"] and this has gotten me much further, into the land
of esoteric template instantiation errors (which I'll try to resolve
before bothering the Boost list, of course... Perhaps needs STLPort...).
Anyway, thanks for the tip, that led directly to the answer to my
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk