From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] status of odroidc2's support?
Date: Mon, 4 Dec 2017 11:24:21 +0100 [thread overview]
Message-ID: <20171204112421.275a5e06@windsurf.lan> (raw)
In-Reply-To: <trinity-c7b00df8-109a-4988-8762-2b7898dda327-1512376040564@3c-app-mailcom-bs15>
Hello,
On Mon, 4 Dec 2017 09:27:20 +0100, daggs wrote:
> strange, when running menuconfig, I see only gcc 6 and gcc 7 in the version selection menu. what am I missing?
> I think the branch already supports gcc5
Meh, it's the recent introduction of Cortex-A35 (commit
e9960da6ec84d0fc4f3d7ef8d9db5b1e29d79358 from Yann, added in Cc) that
broke this.
Due to this commit, Cortex-A35 is now the first AArch64 core, and
therefore the one selected by default instead of Cortex-A53.
So, a defconfig that has just
BR2_aarch64=y
will now build for Cortex-A35 instead of Cortex-A53. However,
Cortex-A35 support was only added in gcc 6.x, so only gcc 6.x/7.x are
allowed.
Dagg, you can for now fix that by selecting Cortex-A53 explicitly in
your defconfig:
BR2_aarch64=y
BR2_cortex_a53=y
Yann, do you think we should add a "default BR2_cortex_a53 if
BR2_aarch64 || BR2_aarch64eb" in the choice ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-04 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 6:35 [Buildroot] status of odroidc2's support? daggs
2017-12-04 8:13 ` Thomas Petazzoni
2017-12-04 8:27 ` daggs
2017-12-04 10:24 ` Thomas Petazzoni [this message]
2017-12-04 20:33 ` Yann E. MORIN
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=20171204112421.275a5e06@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox