From: Florian Weimer <fweimer@redhat.com>
To: Mark Brown <broonie@kernel.org>
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: Fri, 14 Oct 2022 08:15:36 +0200 [thread overview]
Message-ID: <87o7uforqv.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <Y0hz3u8ZNO2yFU2f@sirena.org.uk> (Mark Brown's message of "Thu, 13 Oct 2022 21:23:58 +0100")
* Mark Brown:
>> 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.
For what it's worth, it's devtoolset-11-gcc or gcc-toolset-11-gcc,
depending on the OS version. The “11” is the GCC version, new versions
become available in the fall, about half a year after the upstream
release. Old versions remain installable (even in parallel), but drop
out of official support fairly quickly (at least compared to our usual
support timelines).
Thanks,
Florian
next prev parent reply other threads:[~2022-10-14 6:15 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
2022-10-14 6:15 ` Florian Weimer [this message]
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=87o7uforqv.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=Jason@zx2c4.com \
--cc=broonie@kernel.org \
--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).