From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen 4.4.1 build fails for qemu upstream tag missed
Date: Tue, 09 Sep 2014 14:35:21 +0200 [thread overview]
Message-ID: <540EF409.8060409@m2r.biz> (raw)
In-Reply-To: <540EF0A40200007800032879@mail.emea.novell.com>
Il 09/09/2014 12:20, Jan Beulich ha scritto:
>>>> On 09.09.14 at 12:13, <fabio.fantoni@m2r.biz> wrote:
>> I build xen 4.4.1 from git source today after one week that is available
>> but qemu upstream tag qemu-xen-4.4.1 is still missed and xen build fails
>> (except using qemu binary from distro/custum or changing the line in
>> Config.mk before build).
> Did you check http://xenbits.xen.org/gitweb/?p=qemu-upstream-4.4-testing.git;a=summary?
> I can certainly see the tag there.
>
> Jan
>
Sorry for my mistake I had forgotten that in the patches on my github's
4.4 branch I modify the qemu to unstable to use the 2.0 and the last
rebasedone automatically because without conflict.
prev parent reply other threads:[~2014-09-09 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 10:13 Xen 4.4.1 build fails for qemu upstream tag missed Fabio Fantoni
2014-09-09 10:20 ` Jan Beulich
2014-09-09 12:35 ` Fabio Fantoni [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=540EF409.8060409@m2r.biz \
--to=fabio.fantoni@m2r.biz \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.