Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gcc: add support for gcc 8.1
Date: Wed, 23 May 2018 10:29:07 +0200	[thread overview]
Message-ID: <20180523102907.40ae9992@windsurf> (raw)
In-Reply-To: <71945c16-5343-400c-01fe-44f1d5cb31c2@gmail.com>

Hello,

On Mon, 21 May 2018 17:45:02 +0200, Romain Naour wrote:

> > Could you split up this patch in several patches:
> > 
> >  - One adding the toolchain/Config.in contents for gcc 8.x
> > 
> >  - One adding support for gcc 8.x in package/gcc
> > 
> >  - One adding support for gcc 8.x in toolchain/toolchain-external  
> 
> Previous gcc bump was done in one patch:
> 
> (gcc 7)
> https://git.buildroot.net/buildroot/commit/?id=4314161159ce1556e8c14d1d2e22aaf2a8618b82
> (gcc 6)
> https://git.buildroot.net/buildroot/commit/?id=519d83bfa0442439026db4e71e605a5c1347e566
> 
> I wanted to use the same method but ok I'll split this patch if you want.

I think it makes sense to split it up.

> > It would be good if you could also add a patch to update our default
> > gcc version to 7.x.  
> 
> Ok, this can be done in a followup patch.

Yes it _should_ be done in a separate patch.

> > Maybe it's also time to remove gcc 4.9 and gcc 5.x ? I know when gcc
> > 7.x was added and we changed to gcc 6.x as the default, we should have
> > removed gcc 4.9, but there was some opposition to this. Hopefully we
> > can do this removal now ?  
> 
> See the reply from Arnout and Dagg for gcc 4.9:
> http://patchwork.ozlabs.org/patch/767087
> 
> I'm not sure that the odroidc2 defconfig is able to build with gcc >= 4.9 since
> it's stuck at kernel odroidc2-3.14.y and uboot odroidc2-v2015.01.
> Dagg, what do we do for this board?

So the conclusion from Arnout is to keep 4.9, but to remove gcc 5.
I'm fine with this, so let's do this.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2018-05-23  8:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-05 10:58 [Buildroot] [PATCH] package/gcc: add support for gcc 8.1 Romain Naour
2018-05-20 10:45 ` Thomas Petazzoni
2018-05-21 15:45   ` Romain Naour
2018-05-21 16:42     ` Romain Naour
2018-05-23 22:08       ` Arnout Vandecappelle
2018-07-30 13:09         ` Thomas Petazzoni
2018-05-21 21:52     ` Peter Korsgaard
2018-05-22  7:02       ` Thomas Petazzoni
2018-05-22  7:18       ` daggs
2018-05-22  7:46         ` Peter Korsgaard
2018-05-22  8:16         ` Thomas Petazzoni
2018-05-22 22:08       ` Arnout Vandecappelle
2018-05-23 20:19         ` Romain Naour
2018-05-23 21:34           ` Arnout Vandecappelle
2018-05-22  7:13     ` daggs
2018-05-23  8:29     ` Thomas Petazzoni [this message]
2018-05-23 20:23       ` Romain Naour

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=20180523102907.40ae9992@windsurf \
    --to=thomas.petazzoni@bootlin.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