From: David Woodhouse <dwmw2@infradead.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Olaf Hering" <olaf@aepfle.de>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Anthony Perard" <anthony.perard@citrix.com>,
"Paul Durrant" <paul@xen.org>
Subject: Re: qemu v8.0-rc3 fails to compile with Xen
Date: Wed, 12 Apr 2023 18:55:13 +0100 [thread overview]
Message-ID: <5b5b26ed5e0bb65da86eb88364043d4ba039e5f7.camel@infradead.org> (raw)
In-Reply-To: <CAFEAcA_67X3mEpfNDuShsBK2i+taGZVb3JYf+r_qr3fY+aY74w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
On Wed, 2023-04-12 at 18:32 +0100, Peter Maydell wrote:
> On Wed, 12 Apr 2023 at 17:58, David Woodhouse <dwmw2@infradead.org>
> wrote:
> >
> > On Wed, 2023-04-12 at 18:41 +0200, Olaf Hering wrote:
> > > The error with this patch applied looks like this:
> >
> > Thanks. So I think I fixed that one but there are others. I'll make
> > myself a build environment rather than getting you to help me play
> > whack-a-mole.
>
> Is it worth the effort if this version of Xen
> is old enough that it's outside our standard supported
> build platforms policy?
> https://www.qemu.org/docs/master/about/build-platforms.html
> You could just remove all the no-longer-needed compat code
> instead...
Indeed. I'll rip out everything before 4.7.1, which is plenty ancient
enough and the compat support for it is fairly minimal (and builds fine
here).
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5965 bytes --]
prev parent reply other threads:[~2023-04-12 17:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 10:58 qemu v8.0-rc3 fails to compile with Xen Olaf Hering
2023-04-12 11:46 ` Alex Bennée
2023-04-12 12:20 ` Olaf Hering
2023-04-12 14:05 ` David Woodhouse
2023-04-12 16:41 ` Olaf Hering
2023-04-12 16:57 ` David Woodhouse
2023-04-12 17:32 ` Peter Maydell
2023-04-12 17:55 ` David Woodhouse [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=5b5b26ed5e0bb65da86eb88364043d4ba039e5f7.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=alex.bennee@linaro.org \
--cc=anthony.perard@citrix.com \
--cc=olaf@aepfle.de \
--cc=paul@xen.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.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).