From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9461] odroidc2 - toolchain Linaro AArch64 2016.11 compile error
Date: Sun, 04 Dec 2016 23:01:41 +0000 [thread overview]
Message-ID: <bug-9461-163-a9ZmtXDnoM@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9461-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9461
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
--- Comment #8 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Using a gcc 6.x toolchain with a kernel version too old to support gcc 6.x is
not a Buildroot problem, but a configuration issue. One should either select a
toolchain that uses an older gcc version, or a kernel version that is recent
enough to build properly with gcc 6.x.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2016-12-04 23:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 16:17 [Buildroot] [Bug 9461] New: toolchain Linaro AArch64 2016.11 compile error bugzilla at busybox.net
2016-12-03 16:47 ` [Buildroot] [Bug 9461] " bugzilla at busybox.net
2016-12-03 16:56 ` bugzilla at busybox.net
2016-12-03 17:10 ` bugzilla at busybox.net
2016-12-03 17:30 ` bugzilla at busybox.net
2016-12-04 13:39 ` bugzilla at busybox.net
2016-12-04 19:29 ` bugzilla at busybox.net
2016-12-04 19:32 ` [Buildroot] [Bug 9461] odroidc2 - " bugzilla at busybox.net
2016-12-04 20:30 ` bugzilla at busybox.net
2016-12-04 23:01 ` bugzilla at busybox.net [this message]
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-9461-163-a9ZmtXDnoM@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.