* odd meson failure: Unknown variable "exe_name"
@ 2020-08-23 10:45 Peter Maydell
2020-08-23 10:46 ` Peter Maydell
0 siblings, 1 reply; 4+ messages in thread
From: Peter Maydell @ 2020-08-23 10:45 UTC (permalink / raw)
To: QEMU Developers, Paolo Bonzini
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: odd meson failure: Unknown variable "exe_name"
2020-08-23 10:45 odd meson failure: Unknown variable "exe_name" Peter Maydell
@ 2020-08-23 10:46 ` Peter Maydell
2020-08-23 20:34 ` Paolo Bonzini
0 siblings, 1 reply; 4+ messages in thread
From: Peter Maydell @ 2020-08-23 10:46 UTC (permalink / raw)
To: QEMU Developers, Paolo Bonzini
On Sun, 23 Aug 2020 at 11:45, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> 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.
Dropping the '--enable-trace-backends=...' option lets it pass,
so that's the area where the problem is.
-- PMM
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: odd meson failure: Unknown variable "exe_name"
2020-08-23 10:46 ` Peter Maydell
@ 2020-08-23 20:34 ` Paolo Bonzini
2020-08-27 14:35 ` Stefan Hajnoczi
0 siblings, 1 reply; 4+ messages in thread
From: Paolo Bonzini @ 2020-08-23 20:34 UTC (permalink / raw)
To: Peter Maydell; +Cc: QEMU Developers
[-- Attachment #1: Type: text/plain, Size: 1481 bytes --]
It's a rebase issue from the introduction of fuzzing binaries. I will send
a fix.
Paolo
Il dom 23 ago 2020, 12:54 Peter Maydell <peter.maydell@linaro.org> ha
scritto:
> On Sun, 23 Aug 2020 at 11:45, Peter Maydell <peter.maydell@linaro.org>
> wrote:
> >
> > 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.
>
> Dropping the '--enable-trace-backends=...' option lets it pass,
> so that's the area where the problem is.
>
> -- PMM
>
>
[-- Attachment #2: Type: text/html, Size: 2198 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: odd meson failure: Unknown variable "exe_name"
2020-08-23 20:34 ` Paolo Bonzini
@ 2020-08-27 14:35 ` Stefan Hajnoczi
0 siblings, 0 replies; 4+ messages in thread
From: Stefan Hajnoczi @ 2020-08-27 14:35 UTC (permalink / raw)
To: Paolo Bonzini; +Cc: Peter Maydell, QEMU Developers
On Sun, Aug 23, 2020 at 9:34 PM Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> It's a rebase issue from the introduction of fuzzing binaries. I will send a fix.
I have sent a fix.
Stefan
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-08-27 14:36 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-08-23 10:45 odd meson failure: Unknown variable "exe_name" Peter Maydell
2020-08-23 10:46 ` Peter Maydell
2020-08-23 20:34 ` Paolo Bonzini
2020-08-27 14:35 ` Stefan Hajnoczi
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).