ansaurus

Question

Answer 1

+3 A:

I have had some success with Boost and Sun's CC compiler on Solaris 10, but it is a pain. The main thing to remember is you need,

 -library=stlport4 -features=tmplife -features=tmplrefstatic

in you CXXFLAGS for everything you compile, all the template only libraries I have tried seem to work fine with this,(skip all the libraries which need compiling, see here for details )

This does mean of course, that you will have to rebuild any libraries you need to link to (you would be very lucky if they already used stlport4).

Sadly, this is about the only (tenuously) valid reason for not using Boost :-(

Sun C++ Frontend tails blog

Chris Huang-Leaver 2009-11-30 11:35:33

Compilation wasn't really the problem, especially with 1.41 as they have fixed the build scripts to use stlport4. The problem is with the specific peculiarites of the template metaprogramming constructs.

Hassan Syed 2009-11-30 15:47:55

If you have millions of lines of legacy code built with the old stl, which you have to link to, it's a problem! That said, some of the packages do work with the default compiler settings, Boost::Tokenizer for example.

Chris Huang-Leaver 2009-12-01 11:34:46

@Chris: How about binaries of libraries compiled with the old stl, when you don't have access to the source? Now that's frustrating!

David Thornley 2009-12-09 19:21:55

Answer 2

+2 A:

I've fought through this problem myself in the past, and it's a pain in the rear.

To be slightly more specific on Chris Huang-Leaver's answer, you really need to use STLPort4 on the Sun compilers. The default STL delivered by Sun is incomplete, per their own documentation (I'll track it down at some point). The other options that Chris mentions are helpful, but they're not really the root of the problem.

The good news is that Sun also delivers STLPort version 4 with their compilers, so all you need is to include the "-library=stlport4" flag in order to switch over to it. Why they deliver two versions (one semi-broken) of the STL, rather than just one correct version, is beyond me.

Russell Newquist 2009-11-30 14:38:01

Two words: Legacy code. There's a lot of stuff out there compiled with the old version of the Sun STL, and you can't link libraries compiled with the Sun STL and STLPort. (I've tried.) Some libraries are only available compiled with the old Sun STL (including an Oracle library I really wanted to use about three years ago), and if you're going to use them you're going to use the old broken STL. Yes, I found that extremely frustrating.

David Thornley 2009-12-09 19:21:13

Ah, very good point. I should have thought of that, given my own experiences.

Russell Newquist 2009-12-09 23:50:47

Answer 3

+1 A:

I guess since an exact answer has not been provided I must post one myself.

opensolaris(2009.06) and boost-1.4.1 seem to work well. The ./bjam picks the right switches and boost::mpl seems to work well with the sun compiler present. So, as far as I can tell the mpl documentation on compiler support is quite outdated.

Hassan Syed 2009-12-09 18:48:58

ansaurus

tags:

views:

answers:

Sun C++ Compilers and Boost

related questions