unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 34758@debbugs.gnu.org
Subject: [bug#34758] [PATCH 2/4] gnu: Add vhba.
Date: Mon, 25 Mar 2019 22:10:03 +0100	[thread overview]
Message-ID: <87o95yvexg.fsf@gnu.org> (raw)
In-Reply-To: <87o95zcpwp.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me> (Pierre Neidhardt's message of "Mon, 25 Mar 2019 09:35:34 +0100")

Hi,

Pierre Neidhardt <mail@ambrevar.xyz> skribis:

> 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 wasn’t suggesting a kernel rebuild.  I thought that perhaps it’s
enough to use the makefiles and build machinery directly from the kernel
source tree, without rebuilding the kernel itself.  Dunno if that’s possible.

>> 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 agree, no argument here.  :-)

Thanks,
Ludo’.

  reply	other threads:[~2019-03-25 21:17 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
2019-03-25 21:10           ` Ludovic Courtès [this message]
     [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

  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=87o95yvexg.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=34758@debbugs.gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).