From: briancain <1916394@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1916394] Re: [git] Cannot build qemu: FAILED: target/hexagon/semantics_generated.pyinc
Date: Tue, 09 Mar 2021 17:38:33 -0000 [thread overview]
Message-ID: <161531151341.1437.11086224177365442970.malone@wampee.canonical.com> (raw)
In-Reply-To: 161392715224.29500.2044106040123688461.malonedeb@soybean.canonical.com
Looks like there's a patch proposed that sounds as if it would mitigate
this symptom:
https://mail.gnu.org/archive/html/qemu-devel/2021-03/msg02879.html
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1916394
Title:
[git] Cannot build qemu: FAILED:
target/hexagon/semantics_generated.pyinc
Status in QEMU:
Invalid
Bug description:
Hello.
I'm using Archlinux and I maintain qemu-git AUR package.
I tried to build Qemu at commit
4115aec9af2a3de5fa89a0b1daa12debcd7741ff but it stops with this error
message:
Found ninja-1.10.2 at /usr/bin/ninja
[632/9068] Generating semantics_generated.pyinc with a custom command
FAILED: target/hexagon/semantics_generated.pyinc
@INPUT@ target/hexagon/semantics_generated.pyinc
/bin/sh: line 1: @INPUT@: command not found
[637/9068] Compiling C object fsdev/vi...proxy-helper.p/virtfs-proxy-helper.c.o
ninja: build stopped: subcommand failed.
ninja version: 1.10.2
meson version: 0.57.1
Downgrading meson doesn't change anything.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1916394/+subscriptions
prev parent reply other threads:[~2021-03-09 19:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 17:05 [Bug 1916394] [NEW] [git] Cannot build qemu: FAILED: target/hexagon/semantics_generated.pyinc Frederic Bezies
2021-02-22 10:55 ` [Bug 1916394] " Frederic Bezies
2021-02-22 12:40 ` Frederic Bezies
2021-02-22 21:44 ` briancain
2021-02-23 10:24 ` Frederic Bezies
2021-02-23 17:49 ` briancain
2021-03-04 5:53 ` briancain
2021-03-04 5:55 ` briancain
2021-03-04 7:49 ` Frederic Bezies
2021-03-04 7:58 ` Frederic Bezies
2021-03-04 14:26 ` briancain
2021-03-09 17:38 ` briancain [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=161531151341.1437.11086224177365442970.malone@wampee.canonical.com \
--to=1916394@bugs.launchpad.net \
--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).