From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9461] toolchain Linaro AArch64 2016.11 compile error
Date: Sun, 04 Dec 2016 13:39:16 +0000 [thread overview]
Message-ID: <bug-9461-163-Kcwvyo8UqP@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9461-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9461
--- Comment #5 from romain.naour at gmail.com ---
Hi,
The odroidc2-3.14.y branch on github [1] is still maintained and you have just
to update the git hash to the latest version to fix your build issue.
Also it seems that the Amlogic S905 SoC used in your board [2] is now available
with the latest kernel version (v4.8) [3].
I don't have this board, can you test with the new 3.14 hardkernel or 4.8
kernel version and summit a patch bumping the version ?
[1]
https://github.com/hardkernel/linux/commits/odroidc2-3.14.y/include/linux/compiler-gcc.h
[2] http://www.hardkernel.com/main/products/prdt_info.php
[3]
http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/arch/arm64/Kconfig.platforms?h=linux-4.8.y#n81
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-12-04 13:39 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 [this message]
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
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-Kcwvyo8UqP@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