All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc: add gcc 5.2.0
Date: Thu, 16 Jul 2015 17:59:33 -0300	[thread overview]
Message-ID: <55A81B35.2040200@zacarias.com.ar> (raw)
In-Reply-To: <20150716225639.14772165@free-electrons.com>

On 16/07/15 17:56, Thomas Petazzoni wrote:

> That's not the right way of adding gcc 5.2 support. The gcc
> release numbers have changed: 5 is the major release, and 5.{1,2} are
> the bug fix releases.
>
> Quoting https://gcc.gnu.org/ml/gcc/2015-07/msg00198.html:
>
>    GCC 5.2 is a bug-fix release from the GCC 5 branch
>    containing important fixes for regressions and serious bugs in
>    GCC 5.1 with more than 81 bugs fixed since the previous release.
>
> Therefore, we should instead rename BR2_GCC_VERSION_5_1_X to
> BR2_GCC_VERSION_5_X, and then simply update from 5.1 to 5.2 (keeping
> only 5.2 and removing 5.1), exactly like we were doing when the version
> was changed from 4.9.1 to 4.9.2 for example.
>
> Could you rework your patch in this direction?

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.
Do we still want to step on 5.1 considering this?
Regards.

  reply	other threads:[~2015-07-16 20:59 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 [this message]
2015-07-16 21:10     ` Thomas Petazzoni
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=55A81B35.2040200@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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.