From: patchwork-bot+netdevbpf@kernel.org
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: nathan@kernel.org, ndesaulniers@google.com, llvm@lists.linux.dev,
bpf@vger.kernel.org, andrii@kernel.org, quentin@isovalent.com
Subject: Re: [PATCH] tools: Ignore errors from `which' when searching a GCC toolchain
Date: Tue, 01 Feb 2022 22:10:09 +0000 [thread overview]
Message-ID: <164375340944.14402.9754013878528437003.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220201093119.1713207-1-jean-philippe@linaro.org>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 1 Feb 2022 09:31:20 +0000 you wrote:
> When cross-building tools with clang, we run `which $(CROSS_COMPILE)gcc`
> to detect whether a GCC toolchain provides the standard libraries. It is
> only a helper because some distros put libraries where LLVM does not
> automatically find them. On other systems, LLVM detects the libc
> automatically and does not need this. There, it is completely fine not
> to have a GCC at all, but some versions of `which' display an error when
> the command is not found:
>
> [...]
Here is the summary with links:
- tools: Ignore errors from `which' when searching a GCC toolchain
https://git.kernel.org/bpf/bpf/c/b7892f7d5cb2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-02-01 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 9:31 [PATCH] tools: Ignore errors from `which' when searching a GCC toolchain Jean-Philippe Brucker
2022-02-01 16:01 ` Nathan Chancellor
2022-02-01 22:10 ` patchwork-bot+netdevbpf [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=164375340944.14402.9754013878528437003.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=jean-philippe@linaro.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=quentin@isovalent.com \
/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