Dependencies / compatibility for 2.5 SP

[Cantor, Scott]

On 11/16/11 1:16 PM, "Christopher Bongaarts" <cab at umn.edu> wrote:
>
>I tried to get Alphamail working on Solaris in early 2006, which
>required (actually building) Boost.  I still wake up screaming in the
>middle of the night sometimes.

It was that bad back then, but it actually isn't that bad now. The build
worked for me, minus a couple of libraries that didn't work, without any
special tools or steps, just bootstrap.sh and a build script. But I don't
anticipate needing it built.

The problem is it requires stlport (or GCC), and thus a change to every
other software layer on top.

>But as long as you don't actually have to build it, it's probably not so
>bad.  I do recall having to run the latest Forte compiler with
>up-to-date patches.

The compiler situation isn't a concern any longer.

>Where do you plan to use the Boost code? I.e., what things need to be
>compiled with the stlport4 library?  This is to try to get a better
>handle on the scope of not mixing libCstd.

It doesn't matter what layer I use it, every last piece of C++ linked has
to be built with stlport (or possibly even a different STL, I think Apache
offers one now). The only unaffected layers are C-only libraries. You
can't mix STLs, ever. You can't mix C libs either, but people don't notice
because there's never more than one to use.

Basically, you ldd shibd and mod_shib.so (or whatever) and if you see
libCstd, you're dead.

Same reason you can't mix g++ and CC in the stack, or use a custom
compiler on Linux and still use any OS-supplied C++ code.

The hassle here is that the STL is normally part of the OS, and patched
with it. Using a third party STL is a different animal than I have any
experience with. If you were to package this for Solaris, you'd have to
package stlport also. It isn't much of a package, of course, just one file.

-- Scott