Am 18.04.19 um 13:02 schrieb Laszlo Ersek:
On 04/18/19 07:02, Joachim Durchholz wrote:
Am 17.04.19 um 20:27 schrieb Laszlo Ersek:
So, let's look at your original question again (which was not a problem
statement):
So you need an explicit problem statement to know that somebody might
have
Am 17.04.19 um 20:27 schrieb Laszlo Ersek:
So, let's look at your original question again (which was not a problem
statement):
So you need an explicit problem statement to know that somebody might
have a problem?
what's the reasoning behind "We need a terminal output" in curses.c?
The
Sorry, I'm done having to argue against(!) a person who's stonewalling
me by wilfully ignoring differences ("doesn't work perfectly"
interpreted as "does not work at all"), discounting
just-for-testing-purpose workarounds as if they were actual proposed
solutions ("not a sane approach"),
Am 16.04.19 um 09:24 schrieb Gerd Hoffmann:
On Mon, Apr 15, 2019 at 03:10:09PM -0400, John Snow wrote:
On 4/13/19 5:02 AM, Joachim Durchholz wrote:
Hi all,
what's the reasoning behind "We need a terminal output" in curses.c?
curses needs a terminal.
I commented out the check,
Am 14.04.19 um 20:12 schrieb Peter Maydell:
On Sun, 14 Apr 2019 at 17:08, Joachim Durchholz wrote:
Am 14.04.19 um 03:15 schrieb Max Filippov:
On Sat, Apr 13, 2019 at 8:28 AM Joachim Durchholz wrote:
I did the usual ./configure; make dance.
Then modified a source file (ui/curses.c), called
Am 14.04.19 um 03:15 schrieb Max Filippov:
On Sat, Apr 13, 2019 at 8:28 AM Joachim Durchholz wrote:
I did the usual ./configure; make dance.
Then modified a source file (ui/curses.c), called make again, but didn't
see curses.c recompiled, and the change was indeed ineffective.
make clean; make
Hi all,
I did the usual ./configure; make dance.
Then modified a source file (ui/curses.c), called make again, but didn't
see curses.c recompiled, and the change was indeed ineffective.
make clean; make didn't help either.
Is there a list of make targets anywhere?
I looked in a few places in
Hi all,
what's the reasoning behind "We need a terminal output" in curses.c?
I don't really see a scenario where it's problematic if qemu emits
escape sequences to a pipe.
I have experienced one scenario where it is problematic: It doesn't work
properly with pexpect and expectit (a Python and
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
s/install/git clone/
--
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
10 matches
Mail list logo
