From: Kai <kai.kang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] module.bbclass: check whether CONFIG_MODULES set
Date: Thu, 12 Feb 2026 14:48:06 +0800 [thread overview]
Message-ID: <74289f42-8f6c-435f-a97c-896557bed9b3@windriver.com> (raw)
In-Reply-To: <450d9841bf6504e9f457b9b627006b9bdca25228.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]
On 2/5/26 22:49, Richard Purdie wrote:
> On Thu, 2026-02-05 at 17:08 +0800, Kai wrote:
>> On 2/4/26 23:53, Richard Purdie wrote:
>> I agree the warn conditional isn't quite right. I think it should
>>> be:
>>>
>>> if [ CONFIG_MODULES not set in config ];
>>> bberror Broken config, CONFIG_MODULES not set
>>> exit 1
>>> fi
>>>
>>> so it is basically a sanity test that the config is valid.
>>>
>>> I'm a bit worried about what I'm missing though :/
>>>
>> The original problem is kernel config_modules is disabled, then
>> external modules such as lttng-modules can't be built.
>>
>> Recipe lttng-tools RRECOMMENDS on lttng-modules. If install lttng-
>> tools into image, it fails to build lttng-modules.
>>
>> Kernel config CONFIG_MODULES couldn't be checked whether enabled or
>> disabled after bitbake parse. Then there is no
>> chance to remove lttng-module from the dependencies. That why I check
>> the config during the do_compile and do_install
>> with bbnote and generate empty rpm package.
> That is a bit different to the problem I thought this was addressing (I
> was coming from the rust patches angle).
>
> In that case we probably need to have something like "kernel-modules"
> in KERNEL_FEATURES and we check in the lttng-tools recipes if kernel-
> modules are in KERNEL_FEATURES. The kernel itself can then error if the
> feature is selected but not configured and lttng-modules can fail to
> parse with an error if it isn't set?
I sent a patch to preset LTTNGMODULES with '?='. Then it could be
overridden from conf files to clear it. It should be the one who disable
kernel modules support to break the dependency betweenlttng-modules and
lttng-tools.
Thanks, Kai
>
> lttng-tools is not useful without the module support.
>
> Cheers,
>
> Richard
>
>
>
>
--
Kai Kang
Wind River Linux
[-- Attachment #2: Type: text/html, Size: 2847 bytes --]
prev parent reply other threads:[~2026-02-12 6:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 2:09 [PATCH] module.bbclass: check whether CONFIG_MODULES set kai.kang
2026-02-04 13:46 ` [OE-core] " Bruce Ashfield
2026-02-04 13:58 ` Richard Purdie
2026-02-04 14:02 ` Bruce Ashfield
2026-02-04 14:05 ` Richard Purdie
2026-02-04 14:10 ` Bruce Ashfield
2026-02-04 15:53 ` Richard Purdie
2026-02-05 9:08 ` Kai
2026-02-05 12:58 ` Bruce Ashfield
2026-02-05 14:49 ` Richard Purdie
2026-02-12 6:48 ` Kai [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=74289f42-8f6c-435f-a97c-896557bed9b3@windriver.com \
--to=kai.kang@windriver.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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