From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Andrew Jones <drjones@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] git master build failure
Date: Wed, 15 Jun 2016 12:26:53 +0100 [thread overview]
Message-ID: <57613B7D.2060509@ilande.co.uk> (raw)
In-Reply-To: <20160615102303.vq3n76hfi3ugtjeb@hawk.localdomain>
On 15/06/16 11:23, Andrew Jones wrote:
>> Is that from a clean clone of the repository? I wonder if a change to a
>> generated file isn't being picked up somewhere by "make distclean". My
>> standard build script is this:
>
> Not a clean clone, but a clean build dir. I build in a separate build dir.
> mkdir builddir
> cd builddir
> ../srcdir/configure ...
> make
>
>>
>> make distclean
>> './configure' '--target-list=x86_64-softmmu sparc64-softmmu
>> sparc-softmmu ppc-softmmu arm-softmmu' '--disable-pie'
>
> Tried this config and still compiles for me.
I've just tried it again using a git clone into a fresh directory and an
out-of-tree build similar to as you did above and I still get the failure:
cc -I/home/build/src/qemu/git/x/qemu/tcg
-I/home/build/src/qemu/git/x/qemu/tcg/i386
-I/home/build/src/qemu/git/x/qemu/linux-headers
-I/home/build/src/qemu/git/x/build/linux-headers -I.
-I/home/build/src/qemu/git/x/qemu
-I/home/build/src/qemu/git/x/qemu/include
-I/home/build/src/qemu/git/x/qemu/target-ppc -Itarget-ppc
-I/usr/include/pixman-1 -I/home/build/src/qemu/git/x/qemu/dtc/libfdt
-Werror -m64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings
-Wmissing-prototypes -fno-strict-aliasing -fno-common -Wendif-labels
-Wmissing-include-dirs -Wempty-body -Wnested-externs -Wformat-security
-Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-style-declaration
-Wold-style-definition -Wtype-limits -fstack-protector-all
-I/usr/include/p11-kit-1 -I/usr/include/libpng12
-I../linux-headers -I.. -I/home/build/src/qemu/git/x/qemu/target-ppc
-DNEED_CPU_H -I/home/build/src/qemu/git/x/qemu/include -MMD -MP -MT
target-ppc/timebase_helper.o -MF target-ppc/timebase_helper.d -O2
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g -c -o
target-ppc/timebase_helper.o
/home/build/src/qemu/git/x/qemu/target-ppc/timebase_helper.c
/home/build/src/qemu/git/x/qemu/hw/arm/virt.c: In function
‘virt_2_6_class_init’:
/home/build/src/qemu/git/x/qemu/hw/arm/virt.c:1509:5: error: array
subscript is above array bounds [-Werror=array-bounds]
cc1: all warnings being treated as errors
make[1]: *** [hw/arm/virt.o] Error 1
make[1]: Leaving directory `/home/build/src/qemu/git/x/build/arm-softmmu'
make: *** [subdir-arm-softmmu] Error 2
Not sure if it's a contributing factor but my standard make invocation
tries to build with 2 cores once configure has run, i.e. "make V=1 -j2
install".
ATB,
Mark.
next prev parent reply other threads:[~2016-06-15 11:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 7:14 [Qemu-devel] git master build failure Mark Cave-Ayland
2016-06-15 9:48 ` Andrew Jones
2016-06-15 10:08 ` Mark Cave-Ayland
2016-06-15 10:23 ` Andrew Jones
2016-06-15 11:26 ` Mark Cave-Ayland [this message]
2016-06-15 11:46 ` Mark Cave-Ayland
2016-06-15 12:35 ` Laszlo Ersek
2016-06-17 12:41 ` Mark Cave-Ayland
2016-06-17 12:55 ` Peter Maydell
2016-06-17 19:45 ` Laszlo Ersek
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=57613B7D.2060509@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=drjones@redhat.com \
--cc=peter.maydell@linaro.org \
--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).