From: Quentin Monnet <quentin@isovalent.com>
To: Jean-Philippe Brucker <jean-philippe@linaro.org>,
Shung-Hsi Yu <shung-hsi.yu@suse.com>
Cc: Vincent Li <vincent.mc.li@gmail.com>, bpf <bpf@vger.kernel.org>
Subject: Re: bpf selftest compiling error
Date: Thu, 19 May 2022 13:10:42 +0100 [thread overview]
Message-ID: <b90f2bc7-6405-7eaa-ef54-ebdf031a72b0@isovalent.com> (raw)
In-Reply-To: <YoX97QJ976GelRw6@myrica>
2022-05-19 09:21 UTC+0100 ~ Jean-Philippe Brucker <jean-philippe@linaro.org>
> Hi,
>
> On Wed, May 18, 2022 at 10:51:44PM +0800, Shung-Hsi Yu wrote:
>> On Thu, May 12, 2022 at 06:12:36PM -0700, Vincent Li wrote:
>>> On Thu, May 12, 2022 at 5:49 PM Vincent Li <vincent.mc.li@gmail.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I cloned the bpf-next and tried to compile the bpf selftest.
>>>>
>>>> first I got error
>>>>
>>>> "
>>>> CC /usr/src/bpf
>>>> next/tools/testing/selftests/bpf/tools/build/bpftool/xlated_dumper.o
>>>>
>>>> make[1]: *** No rule to make target
>>>> '/usr/src/bpf-next/tools/include/asm-generic/bitops/find.h', needed by
>>>> '/usr/src/bpf-next/tools/testing/selftests/bpf/tools/build/bpftool/btf_dumper.o'.
>>>> Stop.
>>
>> I also ran into the same issue on bpf-next, and the error seems rather
>> absurd as
>>
>> 1. asm-generic/bitops/find.h was removed back in 47d8c15615c0a "include:
>> move find.h from asm_generic to linux", so perhaps this error has
>> something to do with Makefile.asm-generic
>> 2. normal way of building bpftool with `make tools/bpf/bpftool` still
>> works fine
>>
>> Anyway removing ARCH= CROSS_COMPILE= in the bpf selftests Makefile
>> (reverting change added in ea79020a2d9e "selftests/bpf: Enable
>> cross-building with clang") can be used as a workaround to get the build
>> working again. Adding the commit author to the thread to see if there is
>> better approach available.
>
> Could you share the commands that lead to this error? And did you make
> sure to clean the build tree? I often get errors when building tools
> because my toolchains changed and some dependencies in generated .*.d
> files do not exist anymore.
>
> I can't reproduce this specific error on today's linux-next (but found
> another issue with out-of-tree build that I'll investigate). This is what
> I run, on an x86 host for an x86 target:
>
> $ make defconfig
> $ cat tools/testing/selftests/bpf/config >> .config
> # and enable CONFIG_DEBUG_INFO_BTF
> $ make
> $ make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS=
>
> Thanks,
> Jean
Hi, for what it's worth I also observed the same today in samples/bpf;
but after "make clean" the issue disappeared, and I can't reproduce it
anymore.
Quentin
next prev parent reply other threads:[~2022-05-19 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 0:49 bpf selftest compiling error Vincent Li
2022-05-13 1:12 ` Vincent Li
2022-05-18 14:51 ` Shung-Hsi Yu
2022-05-19 8:21 ` Jean-Philippe Brucker
2022-05-19 12:10 ` Quentin Monnet [this message]
2022-05-19 15:57 ` Shung-Hsi Yu
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=b90f2bc7-6405-7eaa-ef54-ebdf031a72b0@isovalent.com \
--to=quentin@isovalent.com \
--cc=bpf@vger.kernel.org \
--cc=jean-philippe@linaro.org \
--cc=shung-hsi.yu@suse.com \
--cc=vincent.mc.li@gmail.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