From: Mark Brown <broonie@kernel.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
linux-toolchains@vger.kernel.org,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: gcc 5 & 6 & others already out of date?
Date: Thu, 13 Oct 2022 21:23:58 +0100 [thread overview]
Message-ID: <Y0hz3u8ZNO2yFU2f@sirena.org.uk> (raw)
In-Reply-To: <87o7ufwovp.fsf@oldenburg.str.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1561 bytes --]
On Thu, Oct 13, 2022 at 08:38:02PM +0200, Florian Weimer wrote:
> * Mark Brown:
> > On Thu, Oct 13, 2022 at 10:37:21AM -0600, Jason A. Donenfeld wrote:
> > I was looking at your suggestion there - as a Debian user that feels a
> > touch enthusiastic (though practically probably not actually a problem)
> > since it's not too far off the release cadence, current Debian is at GCC
> > 10 and we're not due for another release till sometime next year which
> > will be right on the three years.
> Debian also has Clang 13, presumably for building Rust and Firefox.
Ah, so it does - nice!
> > There does also seem to be a contingent of people running enterprise
> > distros managed by an IT department or whatever who may take a while
> > to get round to pushing out new versions so for example might still
> > for example be running Ubuntu 20.04 rather than 22.04 (never mind the
> > people I know are sitting on 18.04 but that's another thing).
> The enterprise distributions have toolchain modules or toolsets that you
> can install, all nicely integrated. You'd probably consider those
> versions too new. 8-/ I expect it's mostly an education issue, raising
> awareness of what's available from vendors. (glibc versions are a
> different matter, but I don't think dropping support for historic
> versions on build hosts is on the table, so that should be relevant.)
Yeah, I found the ones for SLES easily enough but not the ones for RHEL
or Ubuntu. Perfectly prepared to believe they're there though, it does
seem like sometihng users might want.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-10-13 20:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 1:36 gcc 5 & 6 & others already out of date? Jason A. Donenfeld
2022-10-13 12:22 ` David Laight
2022-10-13 12:59 ` Mark Brown
2022-10-13 15:23 ` Jason A. Donenfeld
2022-10-13 16:18 ` Willy Tarreau
2022-10-14 4:28 ` David Laight
2022-10-14 5:27 ` Willy Tarreau
2022-10-13 16:26 ` Mark Brown
2022-10-13 16:37 ` Jason A. Donenfeld
2022-10-13 16:51 ` Willy Tarreau
2022-10-13 17:16 ` Mark Brown
2022-10-13 18:38 ` Florian Weimer
2022-10-13 20:23 ` Mark Brown [this message]
2022-10-14 6:15 ` Florian Weimer
2022-10-13 18:39 ` Florian Weimer
2022-10-13 21:03 ` Nick Desaulniers
2022-10-14 6:37 ` Florian Weimer
2022-10-13 21:08 ` Nick Desaulniers
2022-10-14 1:31 ` Jason A. Donenfeld
2022-10-14 11:13 ` Mark Brown
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=Y0hz3u8ZNO2yFU2f@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Jason@zx2c4.com \
--cc=fweimer@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).