On Sun, Sep 04, 2005 at 11:22:33PM +1000, skaller wrote: > On Sun, 2005-09-04 at 04:08 -0700, Steve Langasek wrote: > > On Sun, Sep 04, 2005 at 08:06:07PM +1000, skaller wrote:
> > The second part,
> > MIT_KRB5_17 {
> > global:
> > *;
> > }
> > specifies a symbol version to apply to all other exported symbols.
> What is the effect of applying a symbol version? Does this change
> the symbol 'external name'? Or is it a separate attribute,
> in which case, how can a client of the library specify a particular
> symbol version?
Symbol versions are transparent to the application, but when present at
build time the linker binds references to that symbol to the specified
symbol version -- this allows the runtime linker to distinguish between
two different functions with the same name but different
implementations.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
