[ale] c++, dynamic linking etc.

Bjorn Dittmer-Roche bjorn at sccs.swarthmore.edu
Tue Feb 10 11:38:34 EST 2004

On Tue, 10 Feb 2004, Alan Stewart wrote:

> I thought dynamic linking was the default. My ldd output (compiling with
> g++/gcc 2.96) looks like this:
>         libz.so.1 => /usr/lib/libz.so.1 (0x40031000)
>         libtiff.so.3 => /usr/lib/libtiff.so.3 (0x40040000)
>         libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3
> (0x40083000)
>         libm.so.6 => /lib/i686/libm.so.6 (0x400c6000)
>         libc.so.6 => /lib/i686/libc.so.6 (0x42000000)
>         libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x400e8000)
>         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

My understanding, still incomplete though it is, is that for the c++ stuff
dynamic linking is not the default since name mangling can get in the way.
Someone on another list suggested I compile using gcc instead of g++ and
explicitly tell it to use libstdc++. You seem to have solved my problem,
though: can you tell me what your compiler cammand line was for generating
that binary?

Are you building non-GPL code for binaery distrobution as well?

thanks for your help!


More information about the Ale mailing list