Re: how to NOT export symbols in statically linked 3rd party shared libs

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

 



Chris Miller wrote:

> I have created a shared lib and want to make sure I only export those
> symbols that should be accessible from external.
> I manage to do that fine with "#pragma GCC visibility"  switches for all
> my "own" symbols.
> However my lib also statically links OpenSSL and the linker exports all
> symbols in libssl too.
> 
> That is a problem because it creates a symbol collision - so how can I
> keep the linker from also exporting the symbols of libs (*.a) statically
> linked to my shared lib?

You'll need to write a linker script.  There are plenty of examples around,
some even in the gcc sources, or you can ask the binutils list.

Andrew.


[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