From: Tom Musta <tommusta@gmail.com>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Build Broken?
Date: Tue, 13 May 2014 09:17:18 -0500 [thread overview]
Message-ID: <5372296E.60204@gmail.com> (raw)
The current origin/master is not building for me:
LINK qemu-img
qemu-img.o: In function `add_format_to_seq':
/bghome/tmusta/powerisa/qemu/qemu/qemu-img.c:73: undefined reference to `g_sequence_lookup'
collect2: ld returned 1 exit status
make: *** [qemu-img] Error 1
Bisection points me to this:
> git bisect good
1a443c1b8b4314d365e82bddeb1de5b4b1c15fb3 is the first bad commit
commit 1a443c1b8b4314d365e82bddeb1de5b4b1c15fb3
Author: Mike Day <ncmike@ncultra.org>
Date: Mon May 5 12:53:34 2014 -0400
qemu-img: sort block formats in help message
The help message for qemu-img lists the supported block formats, of
which there are 27 as of version 2.0.50. The formats are printed in
the order of their driver's position in a linked list, which appears
random. This patch prints the formats in sorted order, making it
easier to read and to find a specific format in the list.
[Added suggestions from Fam Zheng <famz@redhat.com> to declare variables
at the top of the scope in help() and to omit explicit cast for void*
opaque.
--Stefan]
Signed-off-by: Mike Day <ncmike@ncultra.org>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
It appears that this code is dependent on glib.h function that is newer than one of my build systems
(RHEL 6 update 5, gcc version 4.4.7 20120313 (Red Hat 4.4.7-4))
Is this a known limitation? i.e. is QEMU 2.1 going to prereq a newer version of glib2?
next reply other threads:[~2014-05-13 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 14:17 Tom Musta [this message]
2014-05-13 15:34 ` [Qemu-devel] Build Broken? Michael Tokarev
2014-05-13 15:53 ` Cornelia Huck
2014-05-13 15:55 ` Peter Maydell
2014-05-13 15:58 ` Tom Musta
2014-05-13 16:14 ` Paolo Bonzini
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=5372296E.60204@gmail.com \
--to=tommusta@gmail.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 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.