From: Kurt Garloff <garloff@suse.de>
To: Robert Love <rml@novell.com>
Cc: "Timothy D. Witham" <wookie@osdl.org>,
Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: Announcing Binary Compatibility/Testing
Date: Sun, 17 Oct 2004 23:44:38 +0200 [thread overview]
Message-ID: <20041017214438.GA7202@tpkurt.wlan.garloff.de> (raw)
In-Reply-To: <1097709855.5411.20.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
Hi Robert,
On Wed, Oct 13, 2004 at 07:24:15PM -0400, Robert Love wrote:
> I'd venture, in fact, to say that this effort is very important but does
> not affect the kernel at all. Current "fault" lies in things e.g. like
> the C++ ABI, which is constantly fluctuating (rightly so, to fix bugs,
> but still).
These days, it's mostly libstdc++ which is still developing; the
compiler side (name mangling, layout of virt tables, ...) is quite
stable these days; it's these occasional bugs which are found from
time to time in the most obscure scenarios, which are often overstated.
> Any other incompatibility lies in libraries, but we have library
> versioning. There is nothing wrong with newer libs breaking
> compatibility so long as they have a different soname. Vendors just
> need to ship compat libs and ISV's need to make sure they request the
> right lib and don't touch internals.
Except that we have deeps stacks of libraries these days and things
break apart if you need different versions of one library at the same
time ...
D needs libs C and B, but C needs A and B needs A'.
In reality, the picture is many more levels deep.
Thus breaking libs all the time brings nice challenges for integrators
and ISVs as well. Fortunately, most libs don't do that.
Regards,
--
Kurt Garloff, Director SUSE Labs, Novell Inc.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-10-18 9:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 22:16 Timothy D. Witham
2004-10-13 22:38 ` Timothy D. Witham
2004-10-13 22:39 ` Jeff Garzik
2004-10-13 22:55 ` Timothy D. Witham
2004-10-13 23:24 ` Robert Love
2004-10-13 23:36 ` Timothy D. Witham
2004-10-14 18:32 ` Linus Torvalds
2004-10-14 21:57 ` Diego Calleja
2004-10-15 19:49 ` Matthias Urlichs
2004-10-17 21:44 ` Kurt Garloff [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041017214438.GA7202@tpkurt.wlan.garloff.de \
--to=garloff@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.com \
--cc=wookie@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®