From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Linux-libre
Date: Thu, 29 May 2014 19:08:00 +0200 [thread overview]
Message-ID: <20140529170800.GA14924@debian> (raw)
In-Reply-To: <87wqd48tth.fsf@gnu.org>
On Thu, May 29, 2014 at 05:53:46PM +0200, Ludovic Courtès wrote:
> The problem is that the headers are what libc builds against. It
> doesn’t need the latest version (in fact, we build it with
> --enable-kernel=2.6.30.)
I still do not quite get it. If not necessary, it would albeit be allowed to
have the same versions, no? Then why do we not make this choice and maybe
update to a long term kernel in core-updates as suggested in the discussion
following
http://bugs.gnu.org/14851 ?
How about creating one package linux-libre with two outputs 'out' and
'headers'?
When I noticed that udev was looking for kmod, I started packaging it. The
debian web page states it is a replacement of module-init-tools, and indeed
it seems to contain the same binaries (lsmod etc.). I tried to configure udev
with module-init-tools as an input, but it still asks for kmod. Our linux-libre
package has module-init-tools as an input; should we use kmod instead? Then
if kmod requires the kernel headers, my suggestion of the previous paragraph
would not work.
> I suspect the problem is that linux-libre-headers is build with the
> default config, which may lack some features, and so as a side effect
> some headers are not installed.
> Would you like to look into it? Or maybe Alírio? :-)
I am having a quick look at it, but I would gladly step back for someone more
knowledgeable! My only interest in all this is actually to compile kdelibs;
my bug report that it does not require udev according to its configure phase,
but does not compile without it, has not seen a resolution so far.
Andreas
next prev parent reply other threads:[~2014-05-29 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 14:30 Linux-libre Andreas Enge
2014-05-29 15:53 ` Linux-libre Ludovic Courtès
2014-05-29 17:08 ` Andreas Enge [this message]
2014-05-29 17:27 ` Linux-libre Andreas Enge
2014-05-29 21:37 ` Linux-libre 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=20140529170800.GA14924@debian \
--to=andreas@enge.fr \
--cc=guix-devel@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 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).