From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] build failure with coroutine-gthread
Date: Mon, 08 Aug 2011 16:18:11 +0530 [thread overview]
Message-ID: <8762m89o2c.fsf@skywalker.in.ibm.com> (raw)
In-Reply-To: <CAJSP0QX=-vf4gsr74ha=5CdGr_XqnKnvF-3-HOMSwCbzkMGnLg@mail.gmail.com>
On Mon, 8 Aug 2011 10:29:04 +0100, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Mon, Aug 8, 2011 at 10:01 AM, Aneesh Kumar K.V
> <aneesh.kumar@linux.vnet.ibm.com> wrote:
> >
> >
> > LINK qemu-ga
> > coroutine-gthread.o: In function `coroutine_init':
> > /home/opensource/sources/qemu/qemu-upstream/coroutine-gthread.c:39: undefined reference to `g_thread_init'
> > collect2: ld returned 1 exit status
> >
> > The below patch fix the failure. I also added the patch in the VirtFS
> > pull request.
>
> It appears coroutine-core v7 was merged instead of v8. The
> differences are minor:
> * Bisectability: introduce gthread implementation before ucontext/fibers
> * Depend on gthread, not just glib, for multithreaded programming
>
> Here is the patchwork link to the gthread dependency patch in case a
> committer wants to merge it immediately:
> http://patchwork.ozlabs.org/patch/106810/
>
I added a version that applies to master in the pull request
http://article.gmane.org/gmane.comp.emulators.qemu/112648
Message-id:"87bow09sw1.fsf@skywalker.in.ibm.com"
http://repo.or.cz/w/qemu/v9fs.git/commit/4b76a481ee28166d5f415ef97833c624f4fc0792
-aneesh
next prev parent reply other threads:[~2011-08-08 10:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 9:01 [Qemu-devel] build failure with coroutine-gthread Aneesh Kumar K.V
2011-08-08 9:29 ` Stefan Hajnoczi
2011-08-08 10:48 ` Aneesh Kumar K.V [this message]
2011-08-09 17:28 ` Blue Swirl
2011-08-09 17:46 ` Aneesh Kumar K.V
2011-08-10 9:14 ` Stefan Hajnoczi
2011-08-10 17:24 ` Blue Swirl
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=8762m89o2c.fsf@skywalker.in.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@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).