Buildroot Archive on 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: Fri, 17 Jul 2015 11:31:18 -0300	[thread overview]
Message-ID: <55A911B6.3000502@zacarias.com.ar> (raw)
In-Reply-To: <20150716233017.383ce16b@free-electrons.com>

On 16/07/15 18:30, Thomas Petazzoni wrote:

> Yes, I think skipping 5.2.0 for the time is the best option. As I said,
> it anyway doesn't make much sense to have a compiler that doesn't even
> build a kernel properly for a major architecture like ARM.

Hi.
I've retested and found that i've got a busted versatile launcher script 
(used for webkit testing), after reverting some changes it works just fine.
So 5.2.0 it is, replacing 5.1.0.
Regards.

  reply	other threads:[~2015-07-17 14:31 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
2015-07-16 21:14       ` Gustavo Zacarias
2015-07-16 21:30         ` Thomas Petazzoni
2015-07-17 14:31           ` Gustavo Zacarias [this message]
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=55A911B6.3000502@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox