Re: libtool/ltmain linking wrong stdc++

[Taj Morton]

Taj Morton <tajmorton <at> gmail.com> writes:
> Yes, that would cause problems. I know that a C++ app must only have /one/
> libstdc+ linked into it (or linked because of dependencies, or dependencies of
> dependencies, etc). On my build machine (moria), I'm building Amarok, the KDE
> music player. Amarok is written in C++ and links against kdecore. Moria is
> building 2 binaries, one that is linked against libstdc++.so.5, and one that
> links against libstdc++.so.6.
Let me rephrase this, hopefully in more understandable terms
(s/RPM/Autopackage/g to make the story true):
I'm compiling 2 different RPMs for users of my software. One for users who have
GCC-3.3 based systems. One for users with GCC-3.4 based systems. I have both
GCC-3.3 and 3.4 installed (GCC-3.3 in /opt/gcc-3.3, GCC-3.4 is the system gcc
and is in /usr). My problem is that when I compile my GCC-3.3 RPM, libtool links
against /usr/lib/libstdc++.so, instead of /opt/gcc-3.3/lib/libstdc++.so.

Does that make any more sense?
Thanks,
Taj