From: Joachim Durchholz <jo@durchholz.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1824616] [NEW] Build succeeds despite flex/bison missing
Date: Sat, 13 Apr 2019 08:31:03 -0000 [thread overview]
Message-ID: <155514426371.20376.231958396525560199.malonedeb@soybean.canonical.com> (raw)
Message-ID: <20190413083103.IBzvKBTjgpbSCSc91JSA3FY7HOsIca1w0BYiMb2kGts@z> (raw)
Public bug reported:
I just built qemu using a fresh install, and "make" would report success
despite messages of "flex: command not found" and "bison: command not
found".
I didn't notice any errors, but I don't know whether that's because
there's a workaround in case the tools aren't there, or because I didn't
exercize the code paths that would fail.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1824616
Title:
Build succeeds despite flex/bison missing
Status in QEMU:
New
Bug description:
I just built qemu using a fresh install, and "make" would report
success despite messages of "flex: command not found" and "bison:
command not found".
I didn't notice any errors, but I don't know whether that's because
there's a workaround in case the tools aren't there, or because I
didn't exercize the code paths that would fail.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1824616/+subscriptions
next reply other threads:[~2019-04-13 8:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 8:31 Joachim Durchholz [this message]
2019-04-13 8:31 ` [Qemu-devel] [Bug 1824616] [NEW] Build succeeds despite flex/bison missing Joachim Durchholz
2019-04-13 8:32 ` [Qemu-devel] [Bug 1824616] " Joachim Durchholz
2019-04-13 8:32 ` Joachim Durchholz
2021-04-19 6:01 ` Thomas Huth
2021-05-18 1:01 ` MarcH
2021-05-18 7:12 ` 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=155514426371.20376.231958396525560199.malonedeb@soybean.canonical.com \
--to=jo@durchholz.org \
--cc=1824616@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).