qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: odd meson failure: Unknown variable "exe_name"
Date: Sun, 23 Aug 2020 11:45:04 +0100	[thread overview]
Message-ID: <CAFEAcA-dDW27t7VcV5D=01ckBOD5oerr1XK0an7BemORdyQHHA@mail.gmail.com> (raw)

On my x86-64 Linux box, one of my local build trees turned out not
to work:

$ rm -rf build/x86 && mkdir build/x86 && (cd build/x86 &&
'../../configure'
'--target-list=arm-softmmu,aarch64-softmmu,arm-linux-user,aarch64-linux-user'
'--enable-debug' '--cc=ccache gcc' '--audio-drv-list=pa'
'--with-pkgversion=pm215' '--enable-trace-backends=log,dtrace'
'--enable-docs')

fails with
[...]
Program keycodemapdb/tools/keymap-gen found: YES
Program scripts/decodetree.py found: YES
Program ../scripts/modules/module_block.py found: YES
Program nm found: YES
Program scripts/undefsym.sh found: YES
Program scripts/feature_to_c.sh found: YES

../../meson.build:1030:14: ERROR: Unknown variable "exe_name".

A full log can be found at
/home/petmay01/linaro/qemu-from-laptop/qemu/build/x86/meson-logs/meson-log.txt

ERROR: meson setup failed


This is the same box that's worked fine for merge testing, so
presumably something about the particular set of configure
options is tripping it up.

thanks
-- PMM


             reply	other threads:[~2020-08-23 10:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-23 10:45 Peter Maydell [this message]
2020-08-23 10:46 ` odd meson failure: Unknown variable "exe_name" Peter Maydell
2020-08-23 20:34   ` Paolo Bonzini
2020-08-27 14:35     ` Stefan Hajnoczi

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='CAFEAcA-dDW27t7VcV5D=01ckBOD5oerr1XK0an7BemORdyQHHA@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --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).