From: Quentin Monnet <qmo@kernel.org>
To: "Namhyung Kim" <namhyung@kernel.org>, "Björn Töpel" <bjorn@kernel.org>
Cc: bpf@vger.kernel.org, linux-perf-users@vger.kernel.org,
"Alexandre Ghiti" <alexghiti@rivosinc.com>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
"Jean-Philippe Brucker" <jean-philippe@linaro.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Björn Töpel" <bjorn@rivosinc.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
"David Abdurachmanov" <davidlt@rivosinc.com>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Alexei Starovoitov" <ast@kernel.org>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Martin KaFai Lau" <martin.lau@linux.dev>
Subject: Re: [PATCH] tools: Override makefile ARCH variable if defined, but empty
Date: Thu, 21 Nov 2024 11:29:59 +0000 [thread overview]
Message-ID: <6a960374-0cd2-4de9-8fc6-c8fe21097b6b@kernel.org> (raw)
In-Reply-To: <Zz7Ng9CzrF_ciAz-@google.com>
2024-11-20 22:04 UTC-0800 ~ Namhyung Kim <namhyung@kernel.org>
> On Wed, Nov 20, 2024 at 02:25:22PM +0100, Björn Töpel wrote:
>> Björn Töpel <bjorn@kernel.org> writes:
>>
>>> From: Björn Töpel <bjorn@rivosinc.com>
>>>
>>> There are a number of tools (bpftool, selftests), that require a
>>> "bootstrap" build. Here, a bootstrap build is a build host variant of
>>> a target. E.g., assume that you're performing a bpftool cross-build on
>>> x86 to riscv, a bootstrap build would then be an x86 variant of
>>> bpftool. The typical way to perform the host build variant, is to pass
>>> "ARCH=" in a sub-make. However, if a variable has been set with a
>>> command argument, then ordinary assignments in the makefile are
>>> ignored.
>>>
>>> This side-effect results in that ARCH, and variables depending on ARCH
>>> are not set.
>>>
>>> Workaround by overriding ARCH to the host arch, if ARCH is empty.
>>>
>>> Fixes: 8859b0da5aac ("tools/bpftool: Fix cross-build")
>>> Signed-off-by: Björn Töpel <bjorn@rivosinc.com>
>
> Reviewed-by: Namhyung Kim <namhyung@kernel.org>
Acked-by: Quentin Monnet <qmo@kernel.org>
>> Arnaldo/Palmer/Quentin:
>>
>> A bit unsure what tree this patch should go. It's very important for the
>> RISC-V builds, so maybe via Palmer's RISC-V tree?
>
> I think it'd be best to route this through the bpf tree as it seems the
> main target is bpftool. But given the size and the scope of the change,
> it should be fine with perf-tools or RISC-V tree.
The bpf tree would make sense to me as well (but I don't merge patches
myself; let me Cc BPF maintainers).
Quentin
next prev parent reply other threads:[~2024-11-21 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 19:32 [PATCH] tools: Override makefile ARCH variable if defined, but empty Björn Töpel
2024-11-07 9:13 ` Jean-Philippe Brucker
2024-11-07 10:09 ` Alexandre Ghiti
2024-11-20 13:25 ` Björn Töpel
2024-11-21 6:04 ` Namhyung Kim
2024-11-21 11:29 ` Quentin Monnet [this message]
2024-11-26 19:08 ` Andrii Nakryiko
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=6a960374-0cd2-4de9-8fc6-c8fe21097b6b@kernel.org \
--to=qmo@kernel.org \
--cc=acme@redhat.com \
--cc=alexghiti@rivosinc.com \
--cc=andrii@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bjorn@rivosinc.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davidlt@rivosinc.com \
--cc=jean-philippe@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=martin.lau@linux.dev \
--cc=namhyung@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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;
as well as URLs for NNTP newsgroup(s).