qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Michael Tokarev" <mjt@tls.msk.ru>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: Building tools on unsupported cpu/arch
Date: Mon, 20 Jun 2022 12:31:22 +0200	[thread overview]
Message-ID: <beb38967-f089-c0f2-eb41-f33277e38d44@redhat.com> (raw)
In-Reply-To: <31fb2fcb-6ad0-b769-9ec9-94fba0679065@msgid.tls.msk.ru>

On 30/04/2022 16.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.

Did you ever send a patch for this? I something like this should do the job:

diff a/common-user/meson.build b/common-user/meson.build
--- a/common-user/meson.build
+++ b/common-user/meson.build
@@ -1,3 +1,7 @@
+if not have_user
+   subdir_done()
+endif
+
  common_user_inc += include_directories('host/' / host_arch)

  user_ss.add(files(


> 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?

You could try to use --disable-tcg instead of --enable-tcg-interpreter ... 
but I guess we should improve the logic in configure / meson.build a little 
bit to do that automatically...

I guess Philippe's patch from February should do the job:

  https://lists.gnu.org/archive/html/qemu-devel/2022-02/msg00894.html

Philippe, could you maybe respin that series?

  Thomas



  parent reply	other threads:[~2022-06-20 10:33 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
2022-04-30 17:08   ` Michael Tokarev
2022-06-20 10:31 ` Thomas Huth [this message]
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=beb38967-f089-c0f2-eb41-f33277e38d44@redhat.com \
    --to=thuth@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=mjt@tls.msk.ru \
    --cc=pbonzini@redhat.com \
    --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).