From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: agl@linux.vnet.ibm.com, Stefan Hajnoczi <stefanha@gmail.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Anthony Liguori <aliguori@linux.vnet.ibm.com>,
pmyers@redhat.com, bsarathy@redhat.com
Subject: Re: [Qemu-devel] RFC: Qemu Guest Tools ISO
Date: Thu, 23 Jun 2011 18:52:08 +0300 [thread overview]
Message-ID: <4E036128.3080805@redhat.com> (raw)
In-Reply-To: <4E035AD4.9090603@us.ibm.com>
On 06/23/2011 06:25 PM, Anthony Liguori wrote:
>> Even building the tools would be very hard. In general if you build
>> against libc version y, you cannot expect your code to work against libc
>> version y-1, unless you take special measures. With other libraries the
>> "special measures" may not even be possible.
>
>
> Good libraries provide strong ABI compatibility.
>
> Something like glib clearly documents what version of the library
> functions are available in, if you still to responsibly common
> functions, ABI compatibility should be much of an issue.
I don't know about glib, but glibc only guarantees backward
compatibility, not forward compatibility. If you build against a newer
glibc, your executable may not run with an older glibc, even if the
symbols exist in both.
See [1] which touches on the issue; I don't have a better reference.
[1] ftp://ftp.kernel.org/pub/software/libs/glibc/hjl/compat/index.html
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-06-23 15:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 18:55 [Qemu-devel] RFC: Qemu Guest Tools ISO Michael Roth
2011-06-23 9:29 ` Alon Levy
2011-06-23 11:08 ` Stefan Hajnoczi
2011-06-23 11:38 ` Daniel P. Berrange
2011-06-23 14:46 ` Michael Roth
2011-06-23 12:00 ` Avi Kivity
2011-06-23 14:54 ` Michael Roth
2011-06-23 15:09 ` Avi Kivity
2011-06-23 15:50 ` Michael Roth
2011-06-23 15:25 ` Anthony Liguori
2011-06-23 15:52 ` Avi Kivity [this message]
2011-06-27 0:24 ` Natalia Portillo
2011-06-23 11:31 ` Jan Kiszka
2011-06-23 14:41 ` Michael Roth
2011-06-23 11:14 ` Ronen Hod
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=4E036128.3080805@redhat.com \
--to=avi@redhat.com \
--cc=agl@linux.vnet.ibm.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=bsarathy@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pmyers@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).