From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 34758@debbugs.gnu.org
Subject: [bug#34758] [PATCH 2/4] gnu: Add vhba.
Date: Mon, 25 Mar 2019 09:35:34 +0100 [thread overview]
Message-ID: <87o95zcpwp.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87va09zlrg.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
>> This raises a general, important question: how do we build kernel
>> modules on guix? At the moment, it seems that it's only possible by
>> re-building the kernel.
>
> … or maybe just unpacking the kernel source so you have the makefile
> snippet around? Perhaps that’s enough?
Nope, because we need the "build" folder which is only available after
building the kernel. Re-building the kernel just to build a module
sounds like a waste of time :p
> I’m generally dubious about out-of-tree modules. Given the way kernel
> development works, we’re often talking about modules of poor quality, or
> proprietary modules. Do you know the reason this one is not in the main
> tree?
I don't. I'll investigate a bit.
Anyways, I think it's nice as a _free software distribution_ to make it
accessible to the user to build custom modules.
>> I suggest we add a "build" output to the kernel that can be used as an
>> input to build kernel modules. Maybe I should should an email to
>> guix-devel to ask for more opinions / advice.
>
> Yes, sounds like a good idea.
Will do!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-03-25 8:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 17:26 [bug#34758] [PATCH 1/4] gnu: Add libmirage Pierre Neidhardt
2019-03-05 17:28 ` [bug#34758] [PATCH 2/4] gnu: Add vhba Pierre Neidhardt
2019-03-05 17:28 ` [bug#34758] [PATCH 3/4] gnu: Add cdemu-daemon Pierre Neidhardt
2019-03-22 21:13 ` Ludovic Courtès
2019-03-05 17:28 ` [bug#34758] [PATCH 4/4] gnu: Add cdemu-client Pierre Neidhardt
2019-03-22 21:14 ` Ludovic Courtès
2019-03-22 21:25 ` Pierre Neidhardt
2019-03-22 21:12 ` [bug#34758] [PATCH 2/4] gnu: Add vhba Ludovic Courtès
2019-03-22 21:24 ` Pierre Neidhardt
2019-03-22 21:27 ` Pierre Neidhardt
2019-03-23 14:52 ` Ludovic Courtès
2019-03-25 8:35 ` Pierre Neidhardt [this message]
2019-03-25 21:10 ` Ludovic Courtès
[not found] ` <handler.34758.B.15518068039570.ack@debbugs.gnu.org>
2019-03-05 17:44 ` [bug#34758] Acknowledgement ([PATCH 1/4] gnu: Add libmirage.) Pierre Neidhardt
2019-03-22 21:10 ` [bug#34758] [PATCH 1/4] gnu: Add libmirage Ludovic Courtès
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=87o95zcpwp.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me \
--to=mail@ambrevar.xyz \
--cc=34758@debbugs.gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.