shared libs without linker scripts?

Andrew Bartlett abartlet at
Fri Jun 22 16:50:40 MDT 2012

On Thu, 2012-06-21 at 22:05 -0400, simo wrote:
> On Fri, 2012-06-22 at 08:58 +1000, Andrew Bartlett wrote: 
> > On Thu, 2012-06-21 at 14:22 +0200, Jelmer Vernooij wrote:
> > 
> > > Of course, symbol versioning will help you on Linux, but not all
> > > platforms support symbol versioning.
> > 
> > On this, I'm thinking about the broader implications of running without
> > a version script.  Isn't that what we use to make (eg, as an example
> > that we know has poor internal namespace control) libsmbclient safe, and
> > not expose all our internal guts, even on autoconf?
> > 
> > That is, can we do any shared libs, on any build system safely without
> > it?  
> Symbol versioning is orthobonal to the export list

I could only find the build system code for the gnu ld linker script,
how is the export list specified otherwise?

I can't see any other mechanism that we use - libsmbclient doesn't use
_PUBLIC_ decorators either, so I'm genuinely curious how is this being

Andrew Bartlett
Andrew Bartlett                      
Authentication Developer, Samba Team 

More information about the samba-technical mailing list