From: Gerd Hoffmann <kraxel@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] Re: Xen build broken with current git head
Date: Tue, 30 Jun 2009 11:25:27 +0200 [thread overview]
Message-ID: <4A49DA07.5070905@redhat.com> (raw)
In-Reply-To: <4A49D641.6000206@siemens.com>
On 06/30/09 11:09, Jan Kiszka wrote:
> FYI (sorry, no time to dig into this).
Noticed too. Looks like it tries to build xen on arm now, then fails to
link. I suspect it's somewhere in the Makefile changes.
Juan?
cheers,
Gerd
next prev parent reply other threads:[~2009-06-30 9:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 9:09 [Qemu-devel] Xen build broken with current git head Jan Kiszka
2009-06-30 9:25 ` Gerd Hoffmann [this message]
2009-06-30 14:18 ` [Qemu-devel] " Juan Quintela
2009-06-30 14:28 ` Juan Quintela
2009-06-30 14:32 ` Anthony Liguori
2009-06-30 14:50 ` Juan Quintela
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=4A49DA07.5070905@redhat.com \
--to=kraxel@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).