From: Natanael Copa <ncopa@alpinelinux.org>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Achill Gilgenast <fossdd@pwned.life>
Subject: [REGRESSION] (build) kallsyms.h:21:10: fatal error: execinfo.h: No such file or directory
Date: Tue, 1 Jul 2025 16:13:09 +0200 [thread overview]
Message-ID: <20250701161309.0f7984c3@ncopa-desktop> (raw)
Hi!
Commit c104c16073b7 (Kunit to check the longest symbol length)
introduced a regression that causes build to fail on musl libc systems.
The regression has now tickled down to stable releases and is currently
blocking kernel upgrades for Alpine Linux.
There was a fix proposed[1] which has not yet been applied, and Greg
asked us to get the fix (or revert?) in upstream first before handling
it for stable[2].
Since it appears to take some time to get this fixed, I wonder if
we can revert commit c104c16073b7 (Kunit to check the longest symbol
length) til someone has time to help us work out an acceptable fix?
Thanks!
-nc
[1]: https://lore.kernel.org/stable/DB0OSTC6N4TL.2NK75K2CWE9JV@pwned.life/T/#t
[2]: https://lore.kernel.org/stable/2025070104-ether-wipe-9c19@gregkh/
reply other threads:[~2025-07-01 14:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250701161309.0f7984c3@ncopa-desktop \
--to=ncopa@alpinelinux.org \
--cc=akpm@linux-foundation.org \
--cc=fossdd@pwned.life \
--cc=linux-kernel@vger.kernel.org \
--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