From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [hotfix PATCH-for-8.1] meson: Fix cross-building for RISCV host
Date: Tue, 11 Jul 2023 10:25:12 +0100 [thread overview]
Message-ID: <2a09d9f9-1f50-16e6-14b3-dd4501fb76eb@linaro.org> (raw)
In-Reply-To: <45565778-bab4-36dc-bd97-e7fdd13b3b9c@linaro.org>
On 7/11/23 10:02, Philippe Mathieu-Daudé wrote:
> On 11/7/23 10:54, Philippe Mathieu-Daudé wrote:
>> While when building on native Linux the host architecture
>> is reported as "riscv32" or "riscv64", when cross-compiling
>> it is detected as "riscv". Meson handles the cross-detection
>> but displays a warning:
>>
>> WARNING: Unknown CPU family riscv, please report this at
>> https://github.com/mesonbuild/meson/issues/new
>>
>> Commit 278c1bcef5 was tested on native host but not under
>> cross environment, and now we get there [*]:
>
> Richard, if this works for you, please scratch this " [*]",
> I meant to list "https://gitlab.com/qemu-project/qemu/-/jobs/4627545569#L128" but then
> realized this link will
> expire in few days so be irrelevant in the commit desc.
Thanks. I'll apply this after the current run completes.
r~
prev parent reply other threads:[~2023-07-11 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 8:54 [hotfix PATCH-for-8.1] meson: Fix cross-building for RISCV host Philippe Mathieu-Daudé
2023-07-11 9:02 ` Philippe Mathieu-Daudé
2023-07-11 9:25 ` Richard Henderson [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=2a09d9f9-1f50-16e6-14b3-dd4501fb76eb@linaro.org \
--to=richard.henderson@linaro.org \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).