From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Andrew Randrianasulu <randrianasulu@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Build error with git commit 8eb29f1bf5a974dc4c11d2d1f5e7c7f7a62be116 on x86_64
Date: Mon, 25 Feb 2019 17:19:01 +0100 [thread overview]
Message-ID: <0c9db8ef-a2a5-e634-7461-63fae4bba32d@redhat.com> (raw)
In-Reply-To: <201902230335.59138.randrianasulu@gmail.com>
Hi Andrew,
On 2/23/19 1:35 AM, Andrew Randrianasulu wrote:
> Hello!
>
> I just pulled latest git
>
[...]
>
> and default build with simple ./configure on slackware 14.2 x86-64 box failed
> like this:
>
> root@slax:~/src/qemu# LANG=C make -j 5
> CHK version_gen.h
> CC qobject/block-qdict.o
> CC util/thread-pool.o
> CC util/main-loop.o
> CC util/qemu-timer.o
> CC util/iohandler.o
> CC util/aio-posix.o
> qobject/block-qdict.c: In function 'qdict_array_split':
> qobject/block-qdict.c:259:9: error: 'subqdict' may be used uninitialized in this
> function [-Werror=maybe-uninitialized]
> qlist_append_obj(*dst, subqobj ?: QOBJECT(subqdict));
> ^
That's odd, I can not reproduce with a simple ./configure:
$ cat /etc/slackware-version
Slackware 14.2
$ gcc --version
gcc (GCC) 5.5.0
> LANG=C gcc --version
> gcc (GCC) 5.5.0
> Copyright (C) 2015 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
next prev parent reply other threads:[~2019-02-25 16:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 0:35 [Qemu-devel] Build error with git commit 8eb29f1bf5a974dc4c11d2d1f5e7c7f7a62be116 on x86_64 Andrew Randrianasulu
2019-02-25 14:13 ` Eric Blake
2019-02-25 16:19 ` Philippe Mathieu-Daudé [this message]
2019-02-25 17:29 ` Andrew Randrianasulu
2019-02-26 8:54 ` Thomas Huth
2019-02-26 8:58 ` Andrew Randrianasulu
2019-02-26 9:05 ` Thomas Huth
2019-02-26 9:46 ` Andrew Randrianasulu
2019-02-26 9:58 ` Thomas Huth
2019-02-26 10:44 ` Andrew Randrianasulu
2019-02-26 11:05 ` Peter Maydell
2019-02-26 12:16 ` 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=0c9db8ef-a2a5-e634-7461-63fae4bba32d@redhat.com \
--to=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=randrianasulu@gmail.com \
/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).