Instead of stlport4, you might try building against Apache stdcxx. Boost does not officially support that, but there is a spec file here:
http://pkgbuild.svn.sourceforge.net/viewvc/pkgbuild/spec-files-extra/trunk/SFEboost-stdcxx.spec?view=log If you want, you can change the version number from 1_44 to 1_45; all but a few libraries build. SS starting with 12.1 has a -library=stdcxx4 option. My experience is that Boost built against stlport4 is buggy, the filesystem library, at any rate. With Solaris, it is preferred to build with Sun Studio, and to use gcc only if you can't get something to build with cc/CC. Alex On Wed, 2010-11-17 at 10:39 -0800, Apostolos Syropoulos wrote: > > https://svn.boost.org/trac/boost/ticket/3893 > > > > for another example of a workaround with a somewhat clearer explanation. > > > > I had similar problems when I ported rtorrent. > > > > > The poster of the message in the URL above says that > > Apparently Sun CC with its (ancient) STL is not officially supported by > Boost > but I hope you can consider this patch which at least allows me to use > boost/array.hpp (and, more importantly, many other headers which use it) > in my code which can't be compiled with STLport. > > Thus my claim is made stronger by this ;-) Now what I actually want is the > opposite: > > to be able to compile with g++ and not Sun C++! At any rate, I will try all > options. _______________________________________________ OpenIndiana-discuss mailing list [email protected] http://openindiana.org/mailman/listinfo/openindiana-discuss
