On Thu, 18 Sep 2008 16:23:20 +0200, Vladimir Prus <vladimir@codesourcery.com> wrote:
Boris wrote:
On Thu, 18 Sep 2008 09:50:39 +0200, Simon Atanasyan <atanasyan@gmail.com> wrote:
[...]The -library=stlport4 command line option are missed. Boost library should be built and used with this option.
Thanks, I tried 'bjam --toolset=sun stdlib=sun-stlport -q' which worked! What I don't understand though is why Boost hasn't been configured accordingly for Solaris to use STLport automatically?
Should it? I think that sun experts (Hi Simon!) told that it changes ABI, and old code does not use stlport, so having sun-stlport as default stdlib is not good idea. Of course, I probably totally misremember things; we can probably make stdlib=sun-stlport the default, at least when building C++ Boost itself.
I vote yes. :) I managed to build Boost 1.36.0 on Solaris with both g++ 3.4.6 and Sun C++ 5.9 but only after doing this: => For g++ I had to put this line into ~/user-config.jam: using gcc : : : <linker-type>sun ; Without this line you'll get linker errors as g++ seems to use the wrong linker. Building with g++ also only works with cxxflags=-mcpu=ultrasparc: ./bjam --toolset=gcc cxxflags=-mcpu=ultrasparc But this must only be set of course if Solaris is used on a Sparc machine. => For Sun C++ I had to invoke bjam with: ./bjam --toolset=sun stdlib=sun-stlport Here stdlib=sun-stlport should be the default. I think that's all. I hope I didn't confuse anything as I played around with so many command line options. Boris