Re: aspell upgrade woes
- To: Brian Nelson <pyro@debian.org>, debian-devel@lists.debian.org
- Subject: Re: aspell upgrade woes
- From: "Martin v. Löwis" <martin@v.loewis.de>
- Date: Fri, 22 Jul 2005 09:13:00 +0200
- Message-id: <[🔎] 42E09C7C.1000701@v.loewis.de>
- In-reply-to: <4sNOt-1kR-35@gated-at.bofh.it>
- References: <4senE-8fH-15@gated-at.bofh.it> <4sexe-8kf-3@gated-at.bofh.it> <4sexe-8kf-1@gated-at.bofh.it> <4seGY-8pw-9@gated-at.bofh.it> <4sg62-13b-9@gated-at.bofh.it> <4sgIR-1oS-5@gated-at.bofh.it> <4sE8q-24F-1@gated-at.bofh.it> <4sNOt-1kR-35@gated-at.bofh.it>
Brian Nelson wrote:
> OK, very well then, I'll undo the GCC 4 transition for libaspell15.
Isn't there still a binary-compatibility issue here? I thought that
in an application, there must only be one version of libstdc++,
directly or indirectly. Otherwise, during runtime, symbols may resolve
from the "wrong" libstdc++, causing crashes.
So if libaspell is linked with libstdc++.so.6, and some application
links to both libaspell (through the C API), and libstdc++.so.5 (because
it is a C++ application), this application may crash, as it might pick
up symbol definitions from libstdc++.so.6 - or libaspell might crash
as it picks up some symbols from libstdc++.so.5, and some from
libstdc++.so.6.
Regards,
Martin
Reply to: