From: Paolo Bonzini <pbonzini@redhat.com>
To: Hao Xiang <hao.xiang@bytedance.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"jsnow@redhat.com" <jsnow@redhat.com>
Subject: Re: Configure no longer works after pulling in the latest QEMU commits
Date: Fri, 19 May 2023 10:30:54 +0200 [thread overview]
Message-ID: <81e3dd08-1927-241e-2fe2-343e0f815acb@redhat.com> (raw)
In-Reply-To: <CAAYibXhsM8rWghEtUoehodK1u+SZ5of81vA-gshmTWiH7PvbLg@mail.gmail.com>
On 5/19/23 05:00, Hao Xiang wrote:
> Hi,
>
> After pulling in the QEMU latest commits, I can no longer run the
> "configure" command. Below is the error message I am seeing. I believe
> this is related to this change "configure: create a python venv
> unconditionally".
> I am running on Debian GNU/Linux 11 (bullseye) and 5.15 kernel version.
> What can I do to fix/work around the issue?
Hi,
please try the patch I have Cc'd you on,
"[PATCH] mkvenv: replace distlib.database with importlib.metadata/pkg_resources"
Paolo
next prev parent reply other threads:[~2023-05-19 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 3:00 Configure no longer works after pulling in the latest QEMU commits Hao Xiang
2023-05-19 8:30 ` Paolo Bonzini [this message]
2023-05-19 18:52 ` [External] " Hao Xiang
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=81e3dd08-1927-241e-2fe2-343e0f815acb@redhat.com \
--to=pbonzini@redhat.com \
--cc=hao.xiang@bytedance.com \
--cc=jsnow@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).