Re: [Condor-users] Using condor_compile with STL + third party libraries

[Peter Keller <psilord@xxxxxxxxxxx>]

Hello,

On Mon, Nov 28, 2005 at 03:56:04PM +0100, Daniel R Figueiredo wrote:
> I've been trying to use condor_compile together with g++ to compile and 
> link C++ code that makes use of STL. The code I'm trying to compile also 
> links with a third party library (which has not been compiled with 
> condor_compile). Unfortunately, I keep getting error messages in the link 
> phase to undefined references to functions. However, these references are 
> to classes and methods in the std library.

While there is no theoretical reason why Condor's standard universe cannot 
work with STL, there might be some practical ones. My advice to you would
be to ensure that ALL of your source code that you wish to link together
with condor_compile is compiled with the same compiler revision, including the
third party librariy (_especially_ if it is C++ based).

If you do this with gcc 3.4.4, and things *still* fail to link with
similar undefined reference errors, then things get a little more
complicated.

In effect, there would be an internal STL ABI backwards compatibility
failure between the STL that shipped with the gcc 3.4.4 compiler, and
the STL shipped along with Condor's libstdc++ implementation gotten from
the gcc 3.2.2 compiler.

If this ends up being the case, then you'll have to move to the gcc 3.2.2
compiler and recompile all of the potential C++ libraries you want to link
against before linking everything together with condor_compile.

Thank you.

Peter Keller
Condor Project
UW-Madison