From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: shaqtsui <shaqtsui@163.com>
Cc: help-guix@gnu.org
Subject: Re: Error when Kernel configed with "CONFIG_DEBUG_INFO_BTF=y"
Date: Fri, 17 May 2024 10:33:34 -0400 [thread overview]
Message-ID: <87a5kowls1.fsf@gmail.com> (raw)
In-Reply-To: <875xvf407v.fsf@outlook.com> (shaqtsui@163.com's message of "Wed, 15 May 2024 22:29:56 +0800")
Hi,
shaqtsui <shaqtsui@163.com> writes:
> Hi Guix team,
>
> I am struggling on this error but can not get it resolved.
> Please kindly help.
>
>
> Config code snippet
>
> ```
> (kernel (customize-linux
> #:linux linux-libre-with-bpf
> #:configs '(
> "CONFIG_DEBUG_INFO_BTF=y"
> )))
>
[...]
I think I've answered on IRC in #guix, but in case it didn't reach you,
the reason the configure validation step fails is probably due to a
missing KConfig dependency. CONFIG_DEBUG_INFO_BTF depends on
CONFIG_DEBUG_INFO, among others.
In doubt, you can run 'make menuconfig' from the Linux-libre kernel
source directory in a 'guix shell -D linux-libre ncurses' environment.
There you'll be able to inspect dependencies.
After configuring the kernel to your needs (starting from the base
config of Guix if you like), you can even save a 'defconfig' file, via
'make savedefconfig' and provide that directly to customize-linux.
This way of doing things ensure all the KConfig dependencies are
satisfied and avoids any surprise.
--
Thanks,
Maxim
prev parent reply other threads:[~2024-05-17 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 14:29 Error when Kernel configed with "CONFIG_DEBUG_INFO_BTF=y" shaqtsui
2024-05-17 14:33 ` Maxim Cournoyer [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a5kowls1.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=help-guix@gnu.org \
--cc=shaqtsui@163.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 read-only IMAP folder(s) and NNTP newsgroup(s).