From: Marius Bakke <mbakke@fastmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>, 39643@debbugs.gnu.org
Subject: bug#39643: (Out-of-tree) system kernel modules only found in :out
Date: Tue, 18 Feb 2020 18:26:46 +0100 [thread overview]
Message-ID: <87eeur6c2x.fsf@devup.no> (raw)
In-Reply-To: <87blpx6zmn.fsf@nckx>
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
writes:
> Guix,
>
> After adding (specification->package+output "zfs:module") to my
> system packages, it's still missing from current-system:
>
> $ guix system reconfigure …
>
> $ ls /run/current-system/profile/lib/modules/
> 5.4.0-pf7-4-ed26-M88
>
> That's my horrible custom Linux fork/version/abomination.
> Apologies. The ZFS package simply compiles against Guix's default
> linux-libre-5.4.20-gnu package.
To build out-of-tree modules with a custom kernel I would expect that
you have to rebuild them against your kernel:
(define my-kernel
(package/inherit
linux-libre
...))
(define with-custom-kernel
(package-input-rewriting `((,linux-libre . ,my-kernel))))
(define zfs-with-custom-kernel
(with-custom-kernel zfs))
Alternatively, I see that 'linux-module-build-system' takes a #:linux
argument:
(define zfs-with-my-kernel
(package/inherit
zfs
(arguments (substitute-keyword-arguments (package-arguments zfs))
((#:linux _ #f) my-kernel))))
Will these options work for you, or am I misunderstanding something?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-02-18 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 14:45 bug#39643: (Out-of-tree) system kernel modules only found in :out Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-02-18 11:43 ` Danny Milosavljevic
2020-02-18 17:26 ` Marius Bakke [this message]
2020-02-18 17:34 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
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=87eeur6c2x.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=39643@debbugs.gnu.org \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).