From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: vlc: Update to 2.2.0
Date: Mon, 16 Mar 2015 09:50:25 +0100 [thread overview]
Message-ID: <87wq2h72cu.fsf@gnu.org> (raw)
In-Reply-To: <877fui1aw8.fsf@netris.org> (Mark H. Weaver's message of "Sun, 15 Mar 2015 12:30:15 -0400")
Mark H Weaver <mhw@netris.org> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
[...]
>> Now, I think libc’s --enable-kernel can specify a baseline older than
>> the available kernel headers. So it may be that we can use 3.14 headers
>> but build a libc that assumes a kernel possibly as old as 3.4.
>
> One data point: we're running Guix and also Nginx compiled with Guix on
> Hydra which runs a 2.6.x kernel, and it seems to work.
>
> Another data point: [GNU/]Linux From Scratch uses headers from Linux
> 3.19 and configures GNU libc with --enable-kernel=2.6.32. As I recall
> they've been doing this for years, always using headers from the most
> recent kernel but configuring libc to support older kernels.
>
> and another: Debian currently builds their libc against headers from
> Linux 3.12.6 and with --enable-kernel=2.6.32.
>
> In summary, I think using headers from 3.14 would be fine.
Indeed, so let’s do that.
Thanks for the analysis and confirmation!
Ludo’.
next prev parent reply other threads:[~2015-03-16 8:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150303133207.9875.94018@vcs.savannah.gnu.org>
[not found] ` <E1YSmvg-0002aH-2l@vcs.savannah.gnu.org>
2015-03-06 20:31 ` 01/01: gnu: vlc: Update to 2.2.0 Andreas Enge
2015-03-06 22:34 ` Axel
2015-03-12 20:45 ` Andreas Enge
2015-03-12 23:13 ` Mark H Weaver
2015-03-14 13:43 ` Ludovic Courtès
2015-03-14 16:47 ` Jason Self
2015-03-14 21:56 ` Andreas Enge
2015-03-15 13:41 ` Ludovic Courtès
2015-03-15 16:30 ` Mark H Weaver
2015-03-16 8:50 ` Ludovic Courtès [this message]
2015-03-10 16:28 ` 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=87wq2h72cu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.