qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Claudio Fontana" <claudio.fontana@huawei.com>,
	"Alexander Graf" <agraf@suse.de>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"qemu-devel qemu-devel" <qemu-devel@nongnu.org>,
	"Andreas Schwab" <schwab@suse.de>
Subject: Re: [Qemu-devel] Checking the state of arm64-linux-user
Date: Wed, 30 Oct 2013 14:25:00 +0100 (CET)	[thread overview]
Message-ID: <alpine.LNX.2.00.1310301406230.11100@wotan.suse.de> (raw)
In-Reply-To: <CAFEAcA8bAz4PQRtBhwF55RO8_iA6rqaZ4jZ=Cm18N9-kXTFY0w@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 977 bytes --]

Hi,

On Tue, 29 Oct 2013, Peter Maydell wrote:

> On 29 October 2013 18:55, Alex Bennée <alex.bennee@linaro.org> wrote:
> > I think the problem is arm64 has been posted in several dependant patch
> > sets hence working from a git tree. I think for now I'll take off the
> > -Werror training wheels and see how far it gets.
> 
> http://lists.nongnu.org/archive/html/qemu-devel/2013-09/msg04503.html
> 
> is Alex's patchset which he rebased on to a qemu master,
> so if you can't wait for v2 then that's the one to look at.

Alex's patchset covers only the first part of the whole thing, and so 
misses some instructions and fixes.  If you merely want to use 
qemu-arm64 you're better off using the tree from me.

Alex B.: I'm building that tree with gcc 4.7 and this config:
% ../configure --disable-system --enable-linux-user --disable-werror \
  --static --disable-linux-aio --disable-strip \
  --target-list=arm64-linux-user
% make


Ciao,
Michael.

      reply	other threads:[~2013-10-30 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29 18:20 [Qemu-devel] Checking the state of arm64-linux-user Alex Bennée
2013-10-29 18:26 ` Peter Maydell
2013-10-29 18:55   ` Alex Bennée
2013-10-29 18:58     ` Peter Maydell
2013-10-30 13:25       ` Michael Matz [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=alpine.LNX.2.00.1310301406230.11100@wotan.suse.de \
    --to=matz@suse.de \
    --cc=agraf@suse.de \
    --cc=alex.bennee@linaro.org \
    --cc=claudio.fontana@huawei.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=schwab@suse.de \
    /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).