From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Nathan Chancellor <natechancellor@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Will Deacon <will@kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] kbuild: check the minimum compiler version in Kconfig
Date: Thu, 14 Jan 2021 19:14:56 +0100 [thread overview]
Message-ID: <CANiq72krA1VrVC2ecUCQFAgJC07od8POjpVUoGFYJOHjZ23ckQ@mail.gmail.com> (raw)
In-Reply-To: <20210114042420.229524-1-masahiroy@kernel.org>
On Thu, Jan 14, 2021 at 5:25 AM Masahiro Yamada <masahiroy@kernel.org> wrote:
>
> The cc-version.sh also shows the error if the compiler is old:
>
> $ make defconfig CC=clang-9
> *** Default configuration is based on 'x86_64_defconfig'
> ***
> *** Compiler is too old.
> *** Your Clang version: 9.0.1
> *** Minimum Clang version: 10.0.1
> ***
> scripts/Kconfig.include:46: Sorry, this compiler is unsupported.
That looks nice. Hopefully we can do the same approach for other tools too!
> I put the stub for ICC because I see <linux/compiler-intel.h> although
> I am not sure if building the kernel with ICC is well-supported.
I doubt it, and there seems to be no maintainer listed either. I think
it could be considered for removal in an RFC.
Cheers,
Miguel
next prev parent reply other threads:[~2021-01-14 18:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 4:24 [PATCH v2] kbuild: check the minimum compiler version in Kconfig Masahiro Yamada
2021-01-14 7:54 ` Ilie Halip
2021-01-14 8:09 ` Sedat Dilek
2021-01-14 9:20 ` Masahiro Yamada
2021-01-14 16:49 ` Nathan Chancellor
2021-01-14 15:41 ` kernel test robot
2021-01-14 17:07 ` Nathan Chancellor
2021-01-14 18:14 ` Miguel Ojeda [this message]
2021-01-15 22:54 ` Masahiro Yamada
2021-01-16 1:33 ` Miguel Ojeda
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=CANiq72krA1VrVC2ecUCQFAgJC07od8POjpVUoGFYJOHjZ23ckQ@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=paul.gortmaker@windriver.com \
--cc=torvalds@linux-foundation.org \
--cc=will@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 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.