From: Richard Henderson <richard.henderson@linaro.org>
To: Michael Tokarev <mjt@tls.msk.ru>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: Building tools on unsupported cpu/arch
Date: Sat, 30 Apr 2022 09:57:51 -0700 [thread overview]
Message-ID: <61fb585e-3ca6-b218-750c-9e833edd9f3f@linaro.org> (raw)
In-Reply-To: <31fb2fcb-6ad0-b769-9ec9-94fba0679065@msgid.tls.msk.ru>
On 4/30/22 07:11, Michael Tokarev wrote:
> Hello!
>
> Previously, it was possible to build qemu tools (such as qemu-img, or qemu-ga)
> on an unsupported cpu/architecture. In a hackish way, by specifying
> --enable-tcg-interpreter on the ./configure line.
>
> Today (with 7.0), it does not work anymore, with the following error
> during configure:
>
> common-user/meson.build:1:0: ERROR: Include dir host/unknown does not exist.
>
> This is with --disable-system --disable-linux-user --disable-user.
>
> And without --enable-tcg-interpreter, it gives:
>
> meson.build:390:6: ERROR: Problem encountered: Unsupported CPU m68k, try
> --enable-tcg-interpreter
>
> What's the way to build tools on an unsupported architecture these days?
Hmm, well, there isn't a way. This seems like a bug in common-user/meson.build.
We should not add this include directory if neither linux-user and bsd-user are enabled.
r~
next prev parent reply other threads:[~2022-04-30 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 14:11 Building tools on unsupported cpu/arch Michael Tokarev
2022-04-30 16:57 ` Richard Henderson [this message]
2022-04-30 17:08 ` Michael Tokarev
2022-06-20 10:31 ` Thomas Huth
2022-06-20 10:54 ` Michael Tokarev
2022-06-20 12:07 ` Thomas Huth
2022-07-18 7:39 ` Thomas Huth
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=61fb585e-3ca6-b218-750c-9e833edd9f3f@linaro.org \
--to=richard.henderson@linaro.org \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.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).