Subject: [bug#40430] Don’t attempt to create a module database when none are available

From: Simon Tournier <[email-masked]>
Date: Fri, 21 Feb 2025 23:06:01 +0100

Hi,

Thanks for the report.  It’s old and sorry if this had fallen into the
crack.

For reference: https://issues.guix.gnu.org/issue/40430

On Fri, 12 Jun 2020 at 21:04, Ivan Kozlov <[email-masked]> wrote:
> The intent was to allow a Linux package with CONFIG_MODULES=n to work after 5c79f238634c5adb6657f1b4b1bb4ddb8bb73ef1. There are no modules and no ‘lib/modules’.
>
> Will you accept a patch that changes linux-module-database to skip unsuitable inputs instead?
>
> 21.04.2020, 01:12, "Ludovic Courtès" <[email-masked]>:
>> There were a couple of mistakes in this patch (which is fine, we all
>> make mistakes!), so I reverted it along with explanations:
>>
>>   https://git.savannah.gnu.org/cgit/guix.git/commit/?id=71977a6c59460e029c91741c8b11f3a544a70486
>>
>> What problem were you trying to solve, Ivan? What do you mean by
>> “non-modular kernel”?

What’s the status of this report?

I’m in favor to close it.  WDYT?

Cheers,
simon