Re: -static-libgcc and static libstdc++.a,

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

 



Bob Rossi <bob@xxxxxxxxxx> writes:

> Does it make sense to link in libstdc++.a and leave libgcc
> shared? The goal is maximum portability between different linux
> environments.

It makes sense if you do not plan to dlopen any shared libraries which
themselves depend on libstdc++.so.

> I'm hoping this will keep the c++ shared library symbols private,
> but allow the exception handling to work on the system the software
> is run on.

That by itself won't necessarily keep the C++ shared library symbols
private.  To ensure that they are private you would need to use a
version script a link time.

Ian


[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