From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6650] New: Segmentation fault when trying to build latest buildroot
Date: Thu, 31 Oct 2013 10:12:31 +0000 (UTC) [thread overview]
Message-ID: <bug-6650-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=6650
Summary: Segmentation fault when trying to build latest
buildroot
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: daniel.karlsson at scanreco.se
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 5114
--> https://bugs.busybox.net/attachment.cgi?id=5114
Log output when bug occured
When trying to compile latest buildroot (checked out from git repo 2013-10-31)
with the sama5d3ekdemo_defconfig, I get the following error:
/home/daniel/buildroot-at91/output/toolchain/gcc-4.7.2/libgcc/libgcc2.c: In
function '__absvdi2':
/home/daniel/buildroot-at91/output/toolchain/gcc-4.7.2/libgcc/libgcc2.c:273:1
internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugs.buildroot.net/> for instructions.
make[2]: *** [_absvdi2.o] Error 1
There are more error of the sam type that follows, but this is the first error
detected (see attachment, sorry for some words being in swedish).
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2013-10-31 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 10:12 bugzilla at busybox.net [this message]
2013-10-31 10:46 ` [Buildroot] [Bug 6650] Segmentation fault when trying to build latest buildroot bugzilla at busybox.net
2013-10-31 11:39 ` bugzilla at busybox.net
2013-10-31 12:02 ` bugzilla at busybox.net
2013-10-31 12:10 ` bugzilla at busybox.net
2013-10-31 12:28 ` bugzilla at busybox.net
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=bug-6650-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox