qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Fam Zheng" <famz@redhat.com>, "Alex Bligh" <alex@alex.org.uk>,
	"Michael Tokarev" <mjt@tls.msk.ru>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Lluís Vilanova" <vilanova@ac.upc.edu>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Anthony Liguori" <anthony@codemonkey.ws>,
	"Wayne Xia" <xiawenc@linux.vnet.ibm.com>,
	"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v11 0/8] Shared Library Module Support
Date: Fri, 04 Oct 2013 17:24:43 +0200	[thread overview]
Message-ID: <524EDDBB.6060801@redhat.com> (raw)
In-Reply-To: <CAJSP0QVuvLnjT4V7QVCSk-Eh7BAUV9byyrU6ndhgdrLvCHAHTg@mail.gmail.com>

Il 04/10/2013 16:48, Stefan Hajnoczi ha scritto:
>> >
>>> >> v11:
>>> >>     [04] Link DSO with  -Wl,--enable-new-dtags -Wl,-rpath,'$$ORIGIN' (Richard)
>> >
>> > I don't fully understand the portability issue with this flag yet, is this OK
>> > to keep or should be dropped? Any opinions?
> Ping^2

This was only meant as an idea about how to use shared libraries for
common parts of e.g. SPICE.  It's not yet necessary.

Paolo

> This series will be useful for enabling block drivers with library
> dependencies, so I hope we can merge it soon.  Today, package
> maintainers must make a choice about the "right" set of features to
> include in their QEMU build.  With modules they can simply build
> everything and ship individual packages.

      parent reply	other threads:[~2013-10-04 15:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17  8:54 [Qemu-devel] [PATCH v11 0/8] Shared Library Module Support Fam Zheng
2013-09-17  8:54 ` [Qemu-devel] [PATCH v11 1/8] ui/Makefile.objs: delete unnecessary cocoa.o dependency Fam Zheng
2013-09-17  8:54 ` [Qemu-devel] [PATCH v11 2/8] make.rule: fix $(obj) to a real relative path Fam Zheng
2013-09-17  8:54 ` [Qemu-devel] [PATCH v11 3/8] rule.mak: allow per object cflags and libs Fam Zheng
2013-09-30  5:56   ` Wenchao Xia
2013-09-17  8:54 ` [Qemu-devel] [PATCH v11 4/8] build-sys: introduce common-obj-m and block-obj-m for DSO Fam Zheng
2013-09-17  8:54 ` [Qemu-devel] [PATCH v11 5/8] module: implement module loading Fam Zheng
2013-09-17  8:54 ` [Qemu-devel] [PATCH v11 6/8] Makefile: install modules with "make install" Fam Zheng
2013-09-17  8:54 ` [Qemu-devel] [PATCH v11 7/8] .gitignore: ignore module related files (dll, so, mo) Fam Zheng
2013-09-17  8:54 ` [Qemu-devel] [PATCH v11 8/8] block: convert block drivers linked with libs to modules Fam Zheng
2013-09-26 13:26 ` [Qemu-devel] [PATCH v11 0/8] Shared Library Module Support Fam Zheng
2013-10-04 14:48   ` Stefan Hajnoczi
2013-10-04 15:09     ` Michael Tokarev
2013-10-04 15:24     ` Paolo Bonzini [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=524EDDBB.6060801@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=alex@alex.org.uk \
    --cc=anthony@codemonkey.ws \
    --cc=famz@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.com \
    --cc=vilanova@ac.upc.edu \
    --cc=xiawenc@linux.vnet.ibm.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).