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] gcc: bump 7.x series to 7.2.0
Date: Mon, 21 Aug 2017 23:31:50 +0200	[thread overview]
Message-ID: <20170821233150.28c91c2b@windsurf> (raw)
In-Reply-To: <ad90209d-973e-b3e4-fb76-854f6bbb01e9@mind.be>

Hello,

On Fri, 18 Aug 2017 00:17:56 +0200, Arnout Vandecappelle wrote:

> > @@ -18,9 +18,9 @@ GCC_SITE = $(call github,openrisc,or1k-gcc,$(GCC_VERSION))
> >  GCC_SOURCE = gcc-$(GCC_VERSION).tar.gz
> >  else
> >  GCC_SITE = $(BR2_GNU_MIRROR:/=)/gcc/gcc-$(GCC_VERSION)
> > -# From version 6.4.0 a bz2 release tarball is not provided anymore. Use the xz
> > -# tarball instead.
> > -ifeq ($(BR2_GCC_VERSION_6_X),y)
> > +# From version 6.4.0 and 7.2.0 a bz2 release tarball is not provided
> > +# anymore. Use the xz tarball instead.
> > +ifeq ($(BR2_GCC_VERSION_6_X)$(BR2_GCC_VERSION_7_X),y)  
> 
>  This is not maintainable, at some point we'll have to change it into
> BR2_TOOLCHAIN_GCC_AT_LEAST_6.

Agreed, but I've kept that for a future change. In the future, most gcc
tarballs will be .tar.xz, so what we'll have to special case are the
older versions, not the newer ones :)

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

  reply	other threads:[~2017-08-21 21:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16 20:30 [Buildroot] [PATCH] gcc: bump 7.x series to 7.2.0 Thomas Petazzoni
2017-08-16 20:47 ` Andrey Yurovsky
2017-08-17 17:44 ` Thomas Petazzoni
2017-08-18 16:49   ` Bernd Kuhls
2017-08-17 22:17 ` Arnout Vandecappelle
2017-08-21 21:31   ` Thomas Petazzoni [this message]
2017-08-21 21:31 ` 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=20170821233150.28c91c2b@windsurf \
    --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.