On Wed, Aug 29, 2007 at 09:38:01AM +0200, Loïc Minier wrote: > On Tue, Aug 28, 2007, Steve Langasek wrote: > > I don't understand why the change to no longer export strncasecmp and > > strcasecmp from the ABI is supposed to make a difference here. The symbol > > resolution in balsa should be identical in the existing build as in the new > > build, now that gmime2.2 has dropped the symbols. Is the issue that the > > previous version of gmime2.2 exported these functions with a *different > > ABI* than the standard one provided by glibc?
> I downloaded the two gmime versions (2.2.9, 2.2.10), and the ABI seems > compatible with libc's; I built the two and compared objdump -x and -T > output on the two libs ignoring symbol addresses, and removal of > strcasecmp/ncasecmp was the only change. > The bug in balsa seems to be the consequence of an ABI change beyond > the ELF symbols themselves, this is how I got balsa crashing: > (balsa:8345): GLib-GObject-WARNING **: specified instance size for type > `LibBalsaMimeStreamShared' is smaller than the parent type's `GMimeStreamFs' > instance size > GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT > (object_type)' failed > After I rebuilt balsa against unstable's gmime, it wouldn't trigger > this crash anymore. > I suspect the problem is even older than 2.2.9/2.2.10 as the diff shows > no change in stream related files. > Could you please bin NMU balsa against libgmime-2.0-2-dev/2.2.10-1 to > solve this particular issue? Scheduled, but I am concerned that such a change in an object, if it affects balsa's ability to interface with the library, is an ABI change and should be reflected in the library's soname. -- 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/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
