All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gcc: 4.8.x to 5.x: backport a fix for building gcc with gcc-6
Date: Sun, 15 May 2016 22:17:45 +0200	[thread overview]
Message-ID: <20160515221745.6db55477@free-electrons.com> (raw)
In-Reply-To: <CAHXCMMLLCTp79YOTj0N_U1FfdK0XwYp5dTmnFpBO-sw4OD_QJg@mail.gmail.com>

Hello,

On Sun, 15 May 2016 22:01:12 +0200, Samuel Martin wrote:

> >>  package/gcc/4.8.5/130-build_gcc-5_with_gcc-6.patch | 153 +++++++++++++++++++++
> >>  package/gcc/4.9.3/130-build_gcc-5_with_gcc-6.patch | 153 +++++++++++++++++++++  
> >
> > Isn't it a bit odd to have a patch named "build_gcc-5_with_gcc-6" when
> > in fact you're fixing gcc 4.x ?  
> 
> Well, I just imported the patch from crosstool-ng without renaming it,
> but I did run the build test for the 6 versions of gcc Buildroot
> currently supports:
> - 4.7.4 (deprecated): patch not needed
> - 4.8.5: patch needed
> - 4.9.3: patch needed
> - 5.3.0: patch needed
> - 6.1.0: patch needed

gcc 6 cannot be built with gcc 6 without patches? Plus your patch did
not contain any patch against gcc 6.

> - arc-2015.12 (based on gcc-4.8.5): patch needed
> 
> If you prefer, I can rename them, then repost the patch...

Yes, renaming would be nicer. Just 130-fix-build-with-gcc-6.patch is
fine, for example.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-05-15 20:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-15  5:47 [Buildroot] [PATCH] package/gcc: 4.8.x to 5.x: backport a fix for building gcc with gcc-6 Samuel Martin
2016-05-15 19:17 ` Thomas Petazzoni
2016-05-15 20:01   ` Samuel Martin
2016-05-15 20:17     ` Thomas Petazzoni [this message]
2016-05-16  4:03       ` Samuel Martin

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=20160515221745.6db55477@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.