From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7951] New: gcc 4.9.2 fails to build for sparc-buildroot-linux-gnu
Date: Wed, 18 Mar 2015 00:03:39 +0000 (UTC) [thread overview]
Message-ID: <bug-7951-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=7951
Host: x86_64
Target: sparc-buildroot-linux-gnu
Summary: gcc 4.9.2 fails to build for sparc-buildroot-linux-gnu
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: uwe at hermann-uwe.de
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 5931
--> https://bugs.busybox.net/attachment.cgi?id=5931
build log
gcc 4.9.2 fails to build for sparc-buildroot-linux-gnu (buildroot git HEAD as
of today).
In file included from
../../../../libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:17:0:
../../../../libsanitizer/sanitizer_common/sanitizer_internal_defs.h:257:72:
error: size of array ???assertion_failed__865??? is negative
typedef char IMPL_PASTE(assertion_failed_##_, line)[2*(int)(pred)-1]
^
Full log attached.
--
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:[~2015-03-18 0:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 0:03 bugzilla at busybox.net [this message]
2015-03-18 10:05 ` [Buildroot] [Bug 7951] gcc 4.9.2 fails to build for sparc-buildroot-linux-gnu bugzilla at busybox.net
2015-03-19 15:40 ` bugzilla at busybox.net
2015-03-19 15:40 ` bugzilla at busybox.net
2015-04-09 13:09 ` bugzilla at busybox.net
2015-04-16 11:37 ` 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-7951-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 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.