From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: David Laight <David.Laight@aculab.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Matthew Wilcox <willy@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Segher Boessenkool <segher@kernel.crashing.org>,
Joe Perches <joe@perches.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Albert Ou <aou@eecs.berkeley.edu>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Miguel Ojeda <ojeda@kernel.org>,
Paul Mackerras <paulus@samba.org>,
linux-riscv <linux-riscv@lists.infradead.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Will Deacon <will@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] Raise the minimum GCC version to 5.2
Date: Mon, 3 May 2021 15:10:37 +0200 [thread overview]
Message-ID: <CANiq72nyvrb6ZrVVeaT9py7D_Sv9q-a1HGYH-hNpqfmcCmb4dg@mail.gmail.com> (raw)
In-Reply-To: <fc0c7c092f274ab8b760b3c897830347@AcuMS.aculab.com>
On Mon, May 3, 2021 at 2:20 PM David Laight <David.Laight@aculab.com> wrote:
>
> It would be nice to be able to build current kernels (for local
> use) on the 'new' system - but gcc is already too old.
I have seen such environments too... However, for the kernel in
particular, you could install a newer GCC in the 'new' machine (just
for the kernel builds) or do your kernel builds in a different machine
-- a 'new' 'new' one :)
Cheers,
Miguel
next prev parent reply other threads:[~2021-05-03 13:10 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 15:15 [PATCH] Raise the minimum GCC version to 5.2 Masahiro Yamada
2021-05-01 15:52 ` Miguel Ojeda
2021-05-01 17:38 ` Christophe Leroy
2021-05-02 2:41 ` Joe Perches
2021-05-02 18:30 ` Segher Boessenkool
2021-05-02 20:00 ` Joe Perches
2021-05-02 20:32 ` Segher Boessenkool
2021-05-02 21:05 ` Ali Kaasinen
2021-05-02 21:08 ` Linus Torvalds
2021-05-02 22:30 ` Matthew Wilcox
2021-05-03 7:34 ` Alexander Dahl
2021-05-03 8:54 ` Joe Perches
2021-05-03 9:25 ` Arnd Bergmann
2021-05-03 12:20 ` David Laight
2021-05-03 13:10 ` Miguel Ojeda [this message]
2021-05-04 5:30 ` Alexander Dahl
2021-05-04 6:33 ` Christophe Leroy
2021-05-04 12:07 ` Arnd Bergmann
2021-05-04 13:25 ` Andy Shevchenko
2021-05-03 11:35 ` Arnd Bergmann
2021-05-03 9:49 ` Kirill A. Shutemov
2021-05-02 21:23 ` Joe Perches
2021-05-03 0:44 ` Segher Boessenkool
2021-05-03 9:57 ` Arnd Bergmann
2021-05-04 7:56 ` Ben Dooks
2021-05-04 8:38 ` Miguel Ojeda
2021-05-04 9:22 ` Michal Suchánek
2021-05-04 12:09 ` Miguel Ojeda
2021-05-04 12:17 ` Michal Suchánek
2021-05-04 12:26 ` Christophe Leroy
2021-05-02 18:37 ` Segher Boessenkool
2021-05-03 6:16 ` Christophe Leroy
2021-05-04 2:13 ` Masahiro Yamada
2021-05-04 13:18 ` Andy Shevchenko
2021-05-03 12:27 ` David Sterba
2021-05-15 7:14 ` Pavel Machek
2021-05-15 7:27 ` Joe Perches
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=CANiq72nyvrb6ZrVVeaT9py7D_Sv9q-a1HGYH-hNpqfmcCmb4dg@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=David.Laight@aculab.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=masahiroy@kernel.org \
--cc=ojeda@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=paulus@samba.org \
--cc=segher@kernel.crashing.org \
--cc=torvalds@linux-foundation.org \
--cc=will@kernel.org \
--cc=willy@infradead.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).