marcus.brinkmann at ruhr-uni-bochum.de
Thu Feb 26 18:19:47 CET 2004
At Thu, 26 Feb 2004 18:37:09 +0200,
Nikos Mavroyanopoulos wrote:
> On Thu, Feb 26, 2004 at 04:50:37PM +0100, Marcus Brinkmann wrote:
> > If you are talking about sticking the same version on all symbols in
> > the library depending on the soname of the library, then that is not
> > so difficult (nor is it very difficult to maintain it). However, your
> > intention would then be to _load_ two versions of the library into the
> > same binary. For this to be supported, it is not enough to make all
> > symbols versioned. It must also be guaranteed that the two libraries
> > are not conflicting.
> > I don't know enough about libgcrypt to say if that is possible.
> > Potential trouble makers are signal handling, and anything that
> > accesses task-global state. It's a delicate issue, but worthwhile to
> > look into it. It's a delicate issue, though.
> Does the linux ld's versioning solve all these problems? To enable
> them adding a version string in libgcrypt.version is sufficient.
My reply you quoted above explains why it does not solve the problems.
More information about the Gcrypt-devel