mulitple ABI's

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,
I have a library, liba, supplied by a vendor that uses libstdc++.so.5
but only exposes a "C" interface. 

I am trying to build an application with g++ 4.1.1.

I have two scenarios:
1) Build a C++ application (with g++ 4.1.1) which uses the "C" functions
exported by liba and also uses the Standard C++ Library. So, if I do ldd
on my application I see a dependency on both libstdc++.so.5, because of
liba's dependency, and on libstdc++.so.6.

2) Use liba to build a C++ shared library, libb, with the g++ 4.1.1
compiler. Then, build a C++ application with g++ 4.1.1 that uses the "C"
functions from liba and also uses C++ from libb as well as the Standard
C++ Library. So, again, if I do ldd on my application I see a dependency
on libstdc++.so.5 (from liba's dependency) and libstdc++.so.6 (from
using libb and the Standard C++ Library). For that matter, libb shows a
dependency on libstdc++.so.5 (from liba) and libstdc++.so.6 (because it
uses the Standard C++ Library).

Would either of these scenarios be expected to work correctly in all
cases?

-- Janet


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux