From: Christoph Hellwig <hch@infradead.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Miguel Ojeda <ojeda@kernel.org>,
Fangrui Song <maskray@google.com>,
Michal Marek <michal.lkml@markovi.net>,
Arnd Bergmann <arnd@kernel.org>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
clang-built-linux@googlegroups.com,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 0/2] infer CROSS_COMPILE from ARCH for LLVM=1 LLVM_IAS=1
Date: Thu, 8 Jul 2021 06:49:09 +0100 [thread overview]
Message-ID: <YOaR1ZjToP/kgNsC@infradead.org> (raw)
In-Reply-To: <20210707224310.1403944-1-ndesaulniers@google.com>
On Wed, Jul 07, 2021 at 03:43:08PM -0700, Nick Desaulniers wrote:
> We get constant feedback that the command line invocation of make is too
> long. CROSS_COMPILE is helpful when a toolchain has a prefix of the
> target triple, or is an absolute path outside of $PATH, but it's mostly
> redundant for a given ARCH.
>
> Instead, let's infer it from ARCH, and move some flag handling into a
> new file included from the top level Makefile.
Why only for LLVM? I really hate the mess we currently have with
ARCH and CROSS_COMPILE. Being able to set both in .config (and maybe
even inferring CROSS_COMPILE where possible) would make my life so
much easier.
next prev parent reply other threads:[~2021-07-08 5:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 22:43 Nick Desaulniers
2021-07-07 22:43 ` [PATCH 1/2] Makefile: move initial clang flag handling into scripts/Makefile.clang Nick Desaulniers
2021-07-07 22:43 ` [PATCH 2/2] Makefile: drop CROSS_COMPILE for LLVM=1 LLVM_IAS=1 Nick Desaulniers
2021-07-08 8:08 ` Geert Uytterhoeven
2021-07-08 8:44 ` Masahiro Yamada
2021-07-08 10:21 ` Masahiro Yamada
2021-07-08 11:44 ` Arnd Bergmann
2021-07-08 19:06 ` Nick Desaulniers
2021-07-08 19:02 ` Nick Desaulniers
2021-07-08 19:47 ` Masahiro Yamada
2021-07-08 5:49 ` Christoph Hellwig [this message]
2021-07-08 7:27 ` [PATCH 0/2] infer CROSS_COMPILE from ARCH " Arnd Bergmann
2021-07-08 18:04 ` Nick Desaulniers
2021-07-09 8:07 ` Arnd Bergmann
2021-07-14 18:09 ` Nick Desaulniers
2021-07-14 20:18 ` Arnd Bergmann
2021-07-19 21:10 ` Nick Desaulniers
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=YOaR1ZjToP/kgNsC@infradead.org \
--to=hch@infradead.org \
--cc=arnd@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=maskray@google.com \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®