From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-02-21
Date: Sat, 27 Feb 2016 16:19:06 +0100 [thread overview]
Message-ID: <56D1BE6A.80305@gmail.com> (raw)
In-Reply-To: <20160222150539.0301105e@free-electrons.com>
Hi Thomas, All,
Le 22/02/2016 15:05, Thomas Petazzoni a ?crit :
> Hello,
>
[snip]
>> sh4a | prboom-2.5.0 | NOK | http://autobuild.buildroot.net/results/918d72bd9684a39dc688b143b682f8b5f49f1b26/
>
> r_fps.c:296:1: internal compiler error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <https://support.codesourcery.com/GNUToolchain/> for instructions.
>
> Gaah. A bit of investigation needed, maybe we should simply disable
> prboom with this toolchain.
Prboom add unconditionally -O2 in CFLAGS and triggers a segfault with this
toolchain.
See -0s and -O2 in this command line:
/home/autobuild/instance-0/output/host/usr/bin/sh-linux-gnu-gcc -DHAVE_CONFIG_H
-I. -I.. -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -Wall
-Wno-unused -Wno-switch -Wextra -Wno-missing-field-initializers -Winline
-Wwrite-strings -Wundef -Wbad-function-cast -Wcast-align -Wcast-qual
-Wdeclaration-after-statement -ffast-math -O2 -fomit-frame-pointer -I../src
-I/home/autobuild/instance-0/output/host/usr/sh4a-buildroot-linux-gnu/sysroot/usr/include/SDL
-D_GNU_SOURCE=1 -D_REENTRANT -c r_filter.c
-O2 is added from CFLAGS_OPT in configure.ac, so we need to remove it and
autoreconf prboom to avoid this issue.
But if we use BR2_OPTIMIZE_2 we still have the compiler bug... So it's more a
toolchain issue...
I'm ok to disable prboom with this toolchain.
>
>> bfin | qhull-7.2.0 | NOK | http://autobuild.buildroot.net/results/884bd0fef2f88154da949fa3f4cc04368575183a/
>> bfin | qhull-7.2.0 | NOK | http://autobuild.buildroot.net/results/34f8754e2ddb243aaa73af196622449f655c5213/
>
> Weird:
>
> /home/peko/autobuild/instance-1/output/build/qhull-7.2.0/src/libqhullcpp/QhullSet.h:330: error: expected `;' before 'i'
> /home/peko/autobuild/instance-1/output/build/qhull-7.2.0/src/libqhullcpp/QhullSet.h:331: error: expected `;' before 'e'
> /home/peko/autobuild/instance-1/output/build/qhull-7.2.0/src/libqhullcpp/QhullSet.h:333: error: 'i' was not declared in this scope
> /home/peko/autobuild/instance-1/output/build/qhull-7.2.0/src/libqhullcpp/QhullSet.h:333: error: 'e' was not declared in this scope
>
qhull needs gcc >= 4.4:
http://patchwork.ozlabs.org/patch/589375/
Best regards,
Romain
next prev parent reply other threads:[~2016-02-27 15:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-02-21 Thomas Petazzoni
2016-02-22 14:05 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-02-23 10:12 ` John Keeping
2016-02-23 10:40 ` Jeroen Roovers
2016-02-23 11:03 ` John Keeping
2016-02-23 12:30 ` Thomas Petazzoni
2016-02-24 11:08 ` Eric Limpens
2016-02-24 20:45 ` Arnout Vandecappelle
2016-02-24 20:59 ` Eric Limpens
2016-02-24 21:42 ` Waldemar Brodkorb
2016-02-24 22:09 ` Arnout Vandecappelle
2016-02-27 15:19 ` Romain Naour [this message]
2016-02-27 22:05 ` Bernd Kuhls
2016-03-01 9:38 ` Thomas Petazzoni
2016-02-28 0:17 ` Bernd Kuhls
2016-03-01 9:39 ` Thomas Petazzoni
2016-03-03 13:56 ` Gustavo Zacarias
-- strict thread matches above, loose matches on Subject: below --
2016-02-22 19:05 Olivier Schonken
2016-02-22 21:55 ` Romain Naour
2016-02-22 22:21 ` Thomas Petazzoni
2016-02-23 7:34 ` Olivier Schonken
2016-02-23 8:11 ` Thomas Petazzoni
2016-02-23 11:13 ` Olivier Schonken
2016-02-24 21:30 ` Waldemar Brodkorb
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=56D1BE6A.80305@gmail.com \
--to=romain.naour@gmail.com \
--cc=buildroot@busybox.net \
/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.