From: Petr Pavlu <petr.pavlu@suse.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-modules@vger.kernel.org,
linux-kbuild <linux-kbuild@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: build failure for stablerc
Date: Tue, 26 May 2026 09:31:11 +0200 [thread overview]
Message-ID: <a4ac44fa-146b-4b13-bf42-0c8cff601ed2@suse.com> (raw)
In-Reply-To: <a47f9124-15b3-4dbc-a211-6161eb98406c@gmx.de>
On 5/25/26 9:39 PM, Toralf Förster wrote:
> Hi,
>
> at a small Hetzner VPS at x86 the compilation of the stablerc v7.0.5-1656-ge79d5c5d57c0 fails under Ubuntu-26.04 with
>
> WRAP arch/x86/include/generated/asm/mmiowb.h
> WRAP arch/x86/include/generated/asm/module.lds.h
> WRAP arch/x86/include/generated/asm/rwonce.h
> UPD include/generated/utsrelease.h
> CC /root/linux/tools/objtool/libsubcmd/run-command.o
> HOSTCC scripts/gendwarfksyms/gendwarfksyms.o
> In file included from scripts/gendwarfksyms/gendwarfksyms.c:12:
> scripts/gendwarfksyms/gendwarfksyms.h:6:10: fatal error: dwarf.h: No such file or directory
> 6 | #include <dwarf.h>
> | ^~~~~~~~~
> compilation terminated.
> make[3]: *** [scripts/Makefile.host:131: scripts/gendwarfksyms/gendwarfksyms.o] Error 1
> make[2]: *** [scripts/Makefile.build:548: scripts/gendwarfksyms] Error 2
> make[1]: *** [/root/linux/Makefile:1325: scripts] Error 2
> make[1]: *** Waiting for unfinished jobs....
> CC /root/linux/tools/objtool/libsubcmd/sigchain.o
Gendwarfksyms requires libdw, see Documentation/kbuild/gendwarfksyms.rst
[1]. Is the library and its development files installed on your system?
If you write a trivial program that includes <dwarf.h>, can the compiler
find it in the default search locations?
[1] https://github.com/torvalds/linux/blob/v7.1-rc5/Documentation/kbuild/gendwarfksyms.rst
-- Petr
next prev parent reply other threads:[~2026-05-26 7:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 19:39 build failure for stablerc Toralf Förster
2026-05-26 7:31 ` Petr Pavlu [this message]
2026-05-26 17:17 ` Toralf Förster
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=a4ac44fa-146b-4b13-bf42-0c8cff601ed2@suse.com \
--to=petr.pavlu@suse.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
/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