On Fri, 2007-05-11 at 00:04 +0100, Peter Tribble wrote: > On 5/10/07, Laszlo (Laca) Peter <laca at sun.com> wrote: > > The real trouble is what happens when multiple version of the same > > lib meet in an executable. It happens sometimes and there's no > > easy way to avoid or fix it. Actual examples are the acroread crash > > (caused by a libz collision) and currently various GNOME apps > > crash due to a clash between libexpat in Python and in /usr/sfw. > > The lower level the library, the higher the probability that it'll > > cause troubles. Tck/Tk is probably okay in this regard, but where > > do you draw the line? > > I don't know. But I think something's going to have to be worked > out, and I keep bringing it up in the hope that someone way > smarter than myself will work out a way to cleanly support > multiple versions.
Let me Cc tools-linking, maybe there is some linker magic that can help. AFAIR direct binding can help in some cases. We certainly can't solve this problem with just file system namespacing. Laca
