Re: compilation problem on solaris-gcc with stlport

"vavboostid" wrote in message news:aekhmg+bput@eGroups.com...

bjam_solaris is the executable of bjam I downloaded from the boost site for solaris. I renamed it so I would remember what platform it was for. Yes, I believe the -sBuild lines have no affect, they do not change the errors if I remove them. Why do they have no affect?

Because the variables are case-sensitive. -sBUILD=, as you write later on, is the proper spelling.

How do I compile both debug and release, static and dynamic libraries? I am using the source code for boost 1.28.0.

Not every one of the buildable boost libraries supplies both static and dynamic libraries on all platforms; you'll need to rely on the Jamfiles which specify them to "do the right thing". The <runtime-link> feature controls which C++ runtime library version gets linked to the result, not whether it's static or dynamic. The best you can do is bjam_solaris -a "-sTOOLS=gcc-stlport" "-sBUILD=debug release" -sSTLPORT_ROOT=/core/elements/cots/stlport-4.5.3 HTH, Dave

Thank you very much, Virginia

--- In Boost-Users@y..., "David Abrahams" wrote:

...

"Virginia Volk" wrote in message news:001101c213d1$75c6ca50$b74414ac@v...

...

Does anyone know why I am seeing problems?

I am trying to compile boost on a SunOS 5.6 with gcc 2.95.3,

using

...

...

stlport 4.5.3.

I use the following cmd:

bjam_solaris -a "-sTOOLS=gcc-stlport" "-sBuild= debug release <stlport-iostream>on" "-sBUILD=debug release <runtime-link>static/dynamic" "-sSTLPORT_ROOT=/core/elements/cots/stlport-4.5.3"

That's a pretty confused command-line. The "-sBuild= ..." option will have no effect. What is bjam_solaris?

Looks to me like you're using an old release of Boost. Is this 1.28.0, or something earlier?

-Dave