Re: problem with glibc-2.2.3

[Richard Polton]

It is the dynamic linker, I assume. At least, the libXxf86dga.so is being
linked dynamically into the application. I do not understand how the
symbol versioning works though, so it is not clear to me that I would
pick up address@hidden when looking for atexit.

Thanks,

Richard

Andreas Jaeger wrote:

> Richard Polton <address@hidden> writes:
>
> > Hi,
> >
> > I am experiencing difficulties linking some apps now that I have adopted
> >
> > glibc-2.2.3. Essentially the linker is unable to find 'atexit'.
>
> static or dynamic linker?
>
> > nm libc-2.1.3.so | grep atexit
> > ...
> > 000213fc T atexit
> >
> >
> > nm libc-2.2.3.so | grep atexit
> > ...
> > 00030510 T address@hidden
> >
> >
> > nm libc_nonshared.a | grep atexit
> > ...
> > 00000004 T atexit
> >
> > cat libc.so
> > GROUP ( /lib/libc.so.6 /usr/lib/libc_nonshared.a )
> >
> > where libc.so.6 -> libc-2.2.3.so
> >
> > When linking an application which refers to libXxf86dga.so the linker
> > complains
>
> In that case libXxf86dga.so has no dependency on libc.so.  As you see
> above the atexit is defined in 2.2.3 with version 2.0 and your
> application should reference that.
>
> Andreas
> --
>  Andreas Jaeger
>   SuSE Labs address@hidden
>    private address@hidden
>     http://www.suse.de/~aj