From: Mark Brown <broonie@kernel.org>
To: Valentin Obst <kernel@valentinobst.de>
Cc: Shuah Khan <shuah@kernel.org>,
Anders Roxell <anders.roxell@linaro.org>,
Benjamin Poirier <bpoirier@nvidia.com>,
Guillaume Tucker <guillaume.tucker@collabora.com>,
John Hubbard <jhubbard@nvidia.com>,
Marcos Paulo de Souza <mpdesouza@suse.com>,
Nathan Chancellor <nathan@kernel.org>,
Sasha Levin <sashal@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH RFC] selftests: default to host arch for LLVM builds
Date: Tue, 12 Mar 2024 15:15:41 +0000 [thread overview]
Message-ID: <dcfc27f1-430f-4fe2-b16f-e0bf9c51de5a@sirena.org.uk> (raw)
In-Reply-To: <20240303-selftests-libmk-llvm-rfc-v1-1-9ab53e365e31@valentinobst.de>
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
On Sun, Mar 03, 2024 at 01:44:36PM +0100, Valentin Obst wrote:
> When using gcc without cross compiling, i.e., `CROSS_COMPILE` unset or
> empty, the selftests build defaults to the host architecture, i.e., it uses
> plain gcc. However, when compiling with clang an unset `ARCH` variable in
> combination with an unset `CROSS_COMPILE` variable, i.e., compiling for
> the host architecture, leads to compilation failures since `lib.mk` can
> not determine the clang target triple. In this case, the following error
> message is displayed for each subsystem that does not set `ARCH` in its
> own Makefile before including `lib.mk` (lines wrapped at 75 chrs):
Reviewed-by: Mark Brown <broonie@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-03-12 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 12:44 Valentin Obst
2024-03-12 15:15 ` Mark Brown [this message]
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=dcfc27f1-430f-4fe2-b16f-e0bf9c51de5a@sirena.org.uk \
--to=broonie@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=bpoirier@nvidia.com \
--cc=guillaume.tucker@collabora.com \
--cc=jhubbard@nvidia.com \
--cc=kernel@valentinobst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mpdesouza@suse.com \
--cc=nathan@kernel.org \
--cc=sashal@kernel.org \
--cc=shuah@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
all inboxes | Powered by JetHome®