From: Peter Maydell <peter.maydell@linaro.org>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: "Stefano Stabellini" <sstabellini@kernel.org>,
"Oleksandr Tyshchenko" <oleksandr_tyshchenko@epam.com>,
"Vikram Garhwal" <vikram.garhwal@amd.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Michael Young" <m.a.young@durham.ac.uk>,
qemu-devel@nongnu.org, xen-devel@lists.xenproject.org
Subject: Re: [PATCH] fix qemu build with xen-4.18.0
Date: Tue, 12 Dec 2023 14:36:19 +0000 [thread overview]
Message-ID: <CAFEAcA_1cKWJbjbhnX3A0kjzf_qp7A2rVqPZFHo21dVLb9DutQ@mail.gmail.com> (raw)
In-Reply-To: <8be72952-88b6-4c74-b696-fecfa8313c96@perard>
On Tue, 12 Dec 2023 at 14:20, Anthony PERARD <anthony.perard@citrix.com> wrote:
> Building qemu with something like:
> ./configure --enable-xen --cpu=x86_64
> used to work. Can we fix that? It still works with v8.1.0.
> At least, it works on x86, I never really try to build qemu for arm.
> Notice that there's no "--target-list" on the configure command line.
> I don't know if --cpu is useful here.
You should almost never need to specify --cpu : configure
will work out your host CPU architecture by looking at what
the host compiler defines.
thanks
-- PMM
next prev parent reply other threads:[~2023-12-12 14:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 23:12 [PATCH] fix qemu build with xen-4.18.0 Michael Young
2023-12-08 8:47 ` Richard W.M. Jones
2023-12-08 9:59 ` Richard W.M. Jones
2023-12-08 10:00 ` Richard W.M. Jones
2023-12-08 9:25 ` Daniel P. Berrangé
2023-12-08 10:59 ` Peter Maydell
2023-12-08 11:34 ` Daniel P. Berrangé
2023-12-08 22:49 ` Stefano Stabellini
2023-12-12 14:19 ` Anthony PERARD
2023-12-12 14:36 ` Peter Maydell [this message]
2023-12-12 15:35 ` Volodymyr Babchuk
2023-12-12 15:47 ` Stefan Hajnoczi
2023-12-12 16:02 ` Volodymyr Babchuk
2023-12-12 16:29 ` Stefan Hajnoczi
2023-12-12 16:00 ` Anthony PERARD
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=CAFEAcA_1cKWJbjbhnX3A0kjzf_qp7A2rVqPZFHo21dVLb9DutQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=anthony.perard@citrix.com \
--cc=berrange@redhat.com \
--cc=m.a.young@durham.ac.uk \
--cc=oleksandr_tyshchenko@epam.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=vikram.garhwal@amd.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 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).