From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Volker Rümelin" <vr_qemu@t-online.de>,
qemu-devel <qemu-devel@nongnu.org>,
"Howard Spoelstra" <hsp.cat7@gmail.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 0/7] build: replace ninjatool with ninja
Date: Fri, 16 Oct 2020 10:35:13 +0100 [thread overview]
Message-ID: <eb4db857-3a3c-3deb-e4c8-6e48634fe0ed@ilande.co.uk> (raw)
In-Reply-To: <CABgObfaWkeiLEuigNoL3pmK05fKMbyEjtPG3SV2B4p6ZxEiQDQ@mail.gmail.com>
On 15/10/2020 22:41, Paolo Bonzini wrote:
> Il gio 15 ott 2020, 20:49 Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk
> <mailto:mark.cave-ayland@ilande.co.uk>> ha scritto:
>
> Is there any reason why
> https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg06997.html
> <https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg06997.html> still can't be
> merged?
>
>
> Because it's not the right approach. There is no reason why building firmware cannot
> be done with cross compilers, so moving those directories to Meson (not because Meson
> can't handle them; more specifically, the issue is tying the firmware build to the
> QEMU build system) is going in the wrong direction.
>
> The "Canadian cross" scenario, where you build on Linux a mingw GCC but the compiler
> is s390, is not even enough to describe the complexity in the case of QEMU, because
> there are multiple firmware for different machines.
>
> However we already have all the infrastructure to do such builds, we just don't use
> it for the firmware. So, instead of the patch you recalled above, the tests/tcg
> machinery should be extended into something that can be reused for firmware. As an
> aside, orchestrating this multi-compiler part of the build is what the Makefiles will
> keep on handling for the foreseeable future. As an aside to the aside, tests/tcg is
> more than underdocumented and I forget everything about it 5 minutes after looking at it.
>
> This is not something that I will be able to work on anytime soon. But still I don't
> think that going in the wrong direction is a good idea, even if temporarily.
That's a shame, although I do appreciate the huge amount of time and effort that
you've put into this release in order to get the Meson build up and running, and so
why taking on another large task is going to be lower down the list :)
At the moment OpenBIOS doesn't have a docker image capable of building the required
binaries: I did experiment with trying to use the QEMU docker images for openbios-ppc
but whilst the binary built successfully, it did not run compared to my hand-rolled
compilers. So there's still some debugging to be done there...
ATB,
Mark.
next prev parent reply other threads:[~2020-10-16 9:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 13:54 [PATCH 0/7] build: replace ninjatool with ninja Paolo Bonzini
2020-10-14 13:54 ` [PATCH 1/7] tests/Makefile.include: unbreak non-tcg builds Paolo Bonzini
2020-10-14 16:26 ` Daniel P. Berrangé
2020-10-14 13:54 ` [PATCH 2/7] make: run shell with pipefail Paolo Bonzini
2020-10-14 16:27 ` Daniel P. Berrangé
2020-10-14 13:54 ` [PATCH 3/7] tests: add missing generated sources to testqapi Paolo Bonzini
2020-10-14 16:27 ` Daniel P. Berrangé
2020-10-14 13:54 ` [PATCH 4/7] configure: move QEMU_INCLUDES to meson Paolo Bonzini
2020-10-14 16:28 ` Daniel P. Berrangé
2020-10-14 13:54 ` [PATCH 5/7] dockerfiles: enable Centos 8 PowerTools Paolo Bonzini
2020-10-14 16:33 ` Daniel P. Berrangé
2020-10-14 20:49 ` Cleber Rosa
2020-10-15 6:36 ` Paolo Bonzini
2020-10-14 13:54 ` [PATCH 6/7] add ninja to dockerfiles, CI configurations and test VMs Paolo Bonzini
2020-10-14 16:36 ` Daniel P. Berrangé
2020-10-15 6:50 ` Alex Bennée
2020-10-14 13:54 ` [PATCH 7/7] build: replace ninjatool with ninja Paolo Bonzini
2020-10-14 16:38 ` Daniel P. Berrangé
2020-10-14 13:57 ` [PATCH 0/7] " Peter Maydell
2020-10-15 6:15 ` Howard Spoelstra
2020-10-15 6:34 ` Paolo Bonzini
2020-10-15 7:39 ` Howard Spoelstra
2020-10-15 9:44 ` Paolo Bonzini
2020-10-15 17:39 ` Volker Rümelin
2020-10-15 18:49 ` Mark Cave-Ayland
2020-10-15 21:41 ` Paolo Bonzini
2020-10-16 9:35 ` Mark Cave-Ayland [this message]
2020-10-15 23:07 ` Howard Spoelstra
2020-10-15 18:21 ` 罗勇刚(Yonggang Luo)
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=eb4db857-3a3c-3deb-e4c8-6e48634fe0ed@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=hsp.cat7@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vr_qemu@t-online.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 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.