From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc: add gcc 5.2.0
Date: Thu, 16 Jul 2015 23:10:24 +0200 [thread overview]
Message-ID: <20150716231024.656693cb@free-electrons.com> (raw)
In-Reply-To: <55A81B35.2040200@zacarias.com.ar>
Dear Gustavo Zacarias,
On Thu, 16 Jul 2015 17:59:33 -0300, Gustavo Zacarias wrote:
> Yes, i had a little talk with Yann about it and mostly agree.
> However the diff is big enough (8 MB bzipped) and 5.2 doesn't build a
> bootable kernel for qemu-versatile where 5.1 IIRC does, hence
> introducing a regression.
Gah, not the sort of thing you would expect from a bug fix release :-/
> Do we still want to step on 5.1 considering this?
Then I'm not sure obviously. I see two options here:
* Switch to the policy where we support only one 5.x version at a time
(option named BR2_GCC_VERSION_5_X), and keep 5.1 for now until 5.3
is released, hopefully fixing the major bugs.
* Package gcc 5.2 separately from 5.1. But it's pretty useless to
offer as a package a compiler that is not even capable of building a
kernel that boots.
Opinions?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-16 21:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 20:52 [Buildroot] [PATCH] gcc: add gcc 5.2.0 Gustavo Zacarias
2015-07-16 20:56 ` Thomas Petazzoni
2015-07-16 20:59 ` Gustavo Zacarias
2015-07-16 21:10 ` Thomas Petazzoni [this message]
2015-07-16 21:14 ` Gustavo Zacarias
2015-07-16 21:30 ` Thomas Petazzoni
2015-07-17 14:31 ` Gustavo Zacarias
2015-07-17 14:32 ` Thomas Petazzoni
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=20150716231024.656693cb@free-electrons.com \
--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 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.