From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jeffrin Thalakkottoor <jeffrin@rajagiritech.edu.in>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com
Subject: Re: [PATCH 6.18 000/122] 6.18.9-rc1 review
Date: Fri, 6 Feb 2026 13:31:10 +0100 [thread overview]
Message-ID: <2026020601-persecute-avenging-f539@gregkh> (raw)
In-Reply-To: <CAG=yYwnSJCp6W6+0MGG_aaj+Ao7Qhiza0FKvrP-4wf6f9x1SQQ@mail.gmail.com>
On Fri, Feb 06, 2026 at 05:29:58PM +0530, Jeffrin Thalakkottoor wrote:
> Build error related
> screenshot below.
>
> --------------------<screenshot>-----------------------
>
> $make -j 4
> DESCEND objtool
> DESCEND bpf/resolve_btfids
> INSTALL libsubcmd_headers
> INSTALL libbpf_headers
> INSTALL libsubcmd_headers
> make[5]: *** No rule to make target 'str_error.h', needed by
> '/home/jeffrin/kernel/linux-stable-rc/tools/bpf/resolve_btfids/libbpf/staticobjs/libbpf.o'.
> Stop.
> make[4]: *** [Makefile:152:
> /home/jeffrin/kernel/linux-stable-rc/tools/bpf/resolve_btfids/libbpf/staticobjs/libbpf-in.o]
> Error 2
> make[3]: *** [Makefile:61:
> /home/jeffrin/kernel/linux-stable-rc/tools/bpf/resolve_btfids//libbpf/libbpf.a]
> Error 2
> make[2]: *** [Makefile:76: bpf/resolve_btfids] Error 2
> make[1]: *** [/home/jeffrin/kernel/linux-stable-rc/Makefile:1449:
> tools/bpf/resolve_btfids] Error 2
> make[1]: *** Waiting for unfinished jobs....
> CALL scripts/checksyscalls.sh
> make: *** [Makefile:248: __sub-make] Error 2
> -----------------------<screenshot>---------------------------
What .config causes this?
thanks,
greg k-h
next prev parent reply other threads:[~2026-02-06 12:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 14:39 Greg Kroah-Hartman
2026-02-04 19:08 ` Achill Gilgenast
2026-02-04 19:52 ` Brett A C Sheffield
2026-02-04 20:20 ` Florian Fainelli
2026-02-04 20:27 ` Jon Hunter
2026-02-04 21:39 ` Justin Forbes
2026-02-04 23:08 ` Takeshi Ogasawara
2026-02-05 0:14 ` Peter Schneider
2026-02-05 6:03 ` Luna Jernberg
2026-02-05 7:34 ` Ron Economos
2026-02-05 11:47 ` Mark Brown
2026-02-05 14:33 ` Brett Mastbergen
2026-02-06 1:23 ` Hardik Garg
2026-02-06 4:27 ` Barry K. Nathan
2026-02-06 5:52 ` Shung-Hsi Yu
2026-02-06 8:03 ` Dileep malepu
2026-02-06 9:34 ` Miguel Ojeda
2026-02-06 11:59 ` Jeffrin Thalakkottoor
2026-02-06 12:31 ` Greg Kroah-Hartman [this message]
2026-02-06 13:17 ` Jeffrin Thalakkottoor
2026-02-06 13:20 ` Greg Kroah-Hartman
2026-02-06 13:52 ` Jeffrin Thalakkottoor
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=2026020601-persecute-avenging-f539@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hargar@microsoft.com \
--cc=jeffrin@rajagiritech.edu.in \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--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®