From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot: gcc options
Date: Fri, 15 Nov 2013 10:41:51 +0100 [thread overview]
Message-ID: <CAAXf6LU3kQE2J+3zS-XCBYZ9SkxOSNyEAkV-E0_LQbhq3TP8Rw@mail.gmail.com> (raw)
In-Reply-To: <EADA2943BAC14C4AB625A3550A3BE980096DF2C345@SI-MBX04.de.bosch.com>
Hi Sabri,
On Fri, Nov 15, 2013 at 10:38 AM, Altunbas Sabri (DC-IA/EAH2)
<sabri.altunbas@boschrexroth.de> wrote:
> Hi Thomas,
>
> I defined
>
> ....
> BR2_TARGET_OPTIMIZATION="-pipe -mfmovd -mdalign"
> .....
>
> But I get following errors
>
> ....
> ....
> editors/awk.c: In function 'my_strtod':
> editors/awk.c:746: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.
> make[2]: *** [editors/awk.o] Error 1
> make[1]: *** [editors] Error 2
> make[1]: *** Waiting for unfinished jobs....
> CC coreutils/hostid.o
> CC coreutils/id.o
> CC coreutils/install.o
> CC coreutils/ln.o
> CC coreutils/logname.o
> CC coreutils/ls.o
> CC coreutils/md5_sha1_sum.o
> CC coreutils/mkdir.o
> CC coreutils/mkfifo.o
> CC coreutils/mknod.o
> CC coreutils/mv.o
> CC coreutils/nice.o
> CC coreutils/nohup.o
> CC coreutils/od.o
> CC coreutils/printenv.o
> CC coreutils/printf.o
> coreutils/printf.c: In function 'print_direc':
> coreutils/printf.c:248: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.
> make[2]: *** [coreutils/printf.o] Error 1
> make[2]: *** Waiting for unfinished jobs....
> make[1]: *** [coreutils] Error 2
> make[1]: Leaving directory `/home/tux/aaa/buildroot/sh/output/build/busybox-1.21.1'
> make: *** [/home/tux/aaa/buildroot/sh/output/build/busybox-1.21.1/.stamp_built] Error 2
> tux at lmde ~/aaa/buildroot/sh $
>
Could you provide more details?
Which buildroot version are you using, which toolchain, etc.?
Maybe a .config could be useful too.
Thanks,
Thomas
next prev parent reply other threads:[~2013-11-15 9:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 9:03 [Buildroot] buildroot: gcc options Altunbas Sabri
2013-11-15 9:13 ` Thomas De Schampheleire
2013-11-15 9:38 ` Altunbas Sabri
2013-11-15 9:41 ` Thomas De Schampheleire [this message]
2013-11-15 9:57 ` Altunbas Sabri
2013-11-15 10:02 ` Thomas De Schampheleire
2013-11-15 10:05 ` Altunbas Sabri
2013-11-15 10:10 ` Thomas De Schampheleire
2013-11-15 10:25 ` Altunbas Sabri
2013-11-15 10:38 ` Thomas De Schampheleire
2013-11-19 12:17 ` Altunbas Sabri
2013-11-19 12:30 ` Gustavo Zacarias
2013-11-19 17:23 ` Arnout Vandecappelle
2013-11-20 11:45 ` Gustavo Zacarias
2013-11-20 12:10 ` Altunbas Sabri
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=CAAXf6LU3kQE2J+3zS-XCBYZ9SkxOSNyEAkV-E0_LQbhq3TP8Rw@mail.gmail.com \
--to=patrickdepinguin@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.