[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72kVk5BwAfXmnfKGPwMavfdHNqF1gjq9D-U4TmMipS4yoA@mail.gmail.com>
Date: Thu, 11 Mar 2021 12:15:35 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Nicolas Pitre <nico@...xnic.net>,
Nathan Chancellor <nathan@...nel.org>,
Bernhard Rosenkränzer <bero@...dev.ch>,
Miguel Ojeda <ojeda@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Will Deacon <will@...nel.org>,
clang-built-linux <clang-built-linux@...glegroups.com>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] kbuild: collect minimum tool versions into scripts/min-tool-version.sh
On Thu, Mar 11, 2021 at 11:34 AM Masahiro Yamada <masahiroy@...nel.org> wrote:
>
> Hmm, that is a simple, clean idea.
> Then, we can simply read out the file
>
> $ cat scripts/min_versions/gcc
> 4.9.0
Exactly!
> I do not know how to handle
> per-arch versions in this case.
Perhaps we should just push for 5.1.0 everywhere ;-P
Otherwise, we could still have `min-tool-versions.sh` with something like:
$ cat scripts/min_versions/gcc
4.9.0
$ cat scripts/min_versions/gcc_arm64
5.1.0
$ cat scripts/min-tool-versions.sh
if min_versions/$tool_$arch exists
print that one
else
print the default one: min_versions/$tool
i.e. having the plain files allow us to extend the cases without
listing them explicitly in the script, plus it is anyway useful to
separate data from code :-)
Cheers,
Miguel
Powered by blists - more mailing lists