From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [for-next 3/3] package/gcc: remove gcc 4.9
Date: Wed, 14 Jun 2017 09:06:05 +0200 [thread overview]
Message-ID: <87mv9b9hgi.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170614085657.0d9ab51f@windsurf.lan> (Thomas Petazzoni's message of "Wed, 14 Jun 2017 08:56:57 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Hello,
> On Wed, 14 Jun 2017 07:30:26 +0200, Arnout Vandecappelle wrote:
>> Yeah, that's another reason: if we remove 4.9 from master, than we will not get
>> any fixes for it that could be applied to the LTS branch. But, well, I don't
>> think we're testing with 4.9 at all in the autobuilders so the point is kind of
>> moot.
> We are testing 4.9 in the autobuilders. I rebuilt the pre-built
> toolchains a few days ago. We had two gcc 4.8 toolchains, which I moved
> to 4.9 toolchains. I always try to make sure we have a few "old"
> toolchains, and at least one "bleeding edge" one, just to test more
> configurations.
Sorry, yes indeed - I forgot about your recent mail. We still don't (and
can't) test all binutils/gcc/gdb/linux headers/libc combinations.
> Also, we still have much older external toolchains: remember the recent
> ICU breakage caused by ICU requiring gcc 4.8 ? If such breakage
> occurred, it's because we do have toolchains with gcc's older than 4.8.
Yes, but this discussion was explicitly about support in the internal
toolchain handling for old gcc versions.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-06-14 7:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 18:34 [Buildroot] [for-next 1/3] package/gcc: remove old hashes (gcc 4.5, 4.7, 4.8) Romain Naour
2017-05-25 18:34 ` [Buildroot] [for-next 2/3] package/gcc: switch to gcc 6.x as the default Romain Naour
2017-05-26 13:13 ` Thomas Petazzoni
2017-05-25 18:34 ` [Buildroot] [for-next 3/3] package/gcc: remove gcc 4.9 Romain Naour
2017-05-26 13:14 ` Thomas Petazzoni
2017-06-11 20:30 ` Arnout Vandecappelle
2017-06-13 22:04 ` Peter Korsgaard
2017-06-14 5:30 ` Arnout Vandecappelle
2017-06-14 6:56 ` Thomas Petazzoni
2017-06-14 7:06 ` Peter Korsgaard [this message]
2017-07-01 8:40 ` Romain Naour
2017-06-14 7:03 ` Peter Korsgaard
2017-07-08 6:16 ` daggs
2017-07-09 9:44 ` Romain Naour
2017-05-26 13:13 ` [Buildroot] [for-next 1/3] package/gcc: remove old hashes (gcc 4.5, 4.7, 4.8) 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=87mv9b9hgi.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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.