All of lore.kernel.org
 help / color / mirror / Atom feed
From: MarcH <1824616@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1824616] Re: Build succeeds despite flex/bison missing
Date: Tue, 18 May 2021 01:01:39 -0000	[thread overview]
Message-ID: <162129970021.21294.3706707529064492233.malone@soybean.canonical.com> (raw)
In-Reply-To: 155514426371.20376.231958396525560199.malonedeb@soybean.canonical.com

The warning was supposedly removed by
https://github.com/qemu/qemu/commit/67953a379ea5 /
https://lists.gnu.org/archive/html/qemu-devel/2020-05/msg03980.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/1824616

Title:
  Build succeeds despite flex/bison missing

Status in QEMU:
  Incomplete

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


  parent reply	other threads:[~2021-05-18  1:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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
2021-04-19  6:01 ` Thomas Huth
2021-05-18  1:01 ` MarcH [this message]
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=162129970021.21294.3706707529064492233.malone@soybean.canonical.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.