From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] roseapplepi: backport upstream patches to fix build with gcc 6
Date: Tue, 20 Jun 2017 21:30:08 +0200 [thread overview]
Message-ID: <20170620213008.652bc050@windsurf.lan> (raw)
In-Reply-To: <20170620114952.16292-1-peter@korsgaard.com>
Hello,
On Tue, 20 Jun 2017 13:49:52 +0200, Peter Korsgaard wrote:
> The recent change to default to gcc 6 for the internal toolchain broke this
> defconfig as the u-boot and linux kernel are too old to build with gcc 6.
>
> Fit it by backporting the following commits:
>
> - u-boot: 9b2c282b34 (compiler*.h: sync include/linux/compiler*.h with Linux 4.5-rc6)
> - linux: cb984d101b (compiler-gcc: integrate the various compiler-gcc[345].h files)
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> Andreas F?rber has recently contributed minimal mainline Linux support for
> this SoC, so I'll have a look at migrating to that once it ends up in Linus'
> tree:
I've applied to master. But to be honest, I'm not thrilled with the idea
of adding 1100+ lines of patches just to make one single defconfig build
again with gcc 6.x. If the kernel doesn't build with gcc 6.x, it means
the HW platform is poorly maintained, and it will become worse and
worse.
Perhaps for such platforms we should change the defconfig to use gcc
5.x (or whatever older version works). And once we remove the support
for those older gcc versions, drop the defconfig as well.
What do you think?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-06-20 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 11:49 [Buildroot] [PATCH] roseapplepi: backport upstream patches to fix build with gcc 6 Peter Korsgaard
2017-06-20 19:30 ` Thomas Petazzoni [this message]
2017-06-20 20:04 ` Peter Korsgaard
2017-06-20 20:19 ` Thomas Petazzoni
2017-06-20 20:31 ` Peter Korsgaard
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=20170620213008.652bc050@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