From: Marius Bakke <mbakke@fastmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: ‘core-updates’ is back!
Date: Wed, 30 Aug 2017 23:51:52 +0200 [thread overview]
Message-ID: <877exklo5j.fsf@fastmail.com> (raw)
In-Reply-To: <87k21kg3gk.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 640 bytes --]
Ricardo Wurmus <rekado@elephly.net> writes:
> Marius Bakke <mbakke@fastmail.com> writes:
>
>> Probably unrelated, but we also have to change the '--enable-kernel'
>> configure flag to say '3.2.0' since that is the minimum supported by
>> glibc 2.26.
>
> Does this mean that binaries built with Guix will need at least Linux
> 3.2.0 to be executed?
I believe so, according to the release notes[0]:
* Linux kernel 3.2 or later is required at runtime, on all architectures
supported by that kernel. (This is a change from version 2.25 only for
x86-32 and x86-64.)
[0] https://lists.gnu.org/archive/html/info-gnu/2017-08/msg00000.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-08-30 21:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 22:01 ‘core-updates’ is back! Ludovic Courtès
2017-08-29 8:44 ` Efraim Flashner
2017-08-30 9:30 ` Efraim Flashner
2017-08-30 19:10 ` Marius Bakke
2017-08-30 20:16 ` Efraim Flashner
2017-08-30 20:37 ` Marius Bakke
2017-08-31 14:44 ` Ludovic Courtès
2017-08-31 16:23 ` Marius Bakke
2017-08-31 17:18 ` Marius Bakke
2017-09-02 11:18 ` Marius Bakke
2017-09-02 21:01 ` Ludovic Courtès
2017-08-30 21:17 ` Ricardo Wurmus
2017-08-30 21:51 ` Marius Bakke [this message]
2017-08-29 9:14 ` Andy Wingo
2017-08-29 10:01 ` Ricardo Wurmus
2017-08-29 13:36 ` 宋文武
2017-08-30 9:58 ` Ludovic Courtès
2017-08-30 9:58 ` Ludovic Courtès
2017-09-05 13:21 ` Ricardo Wurmus
2017-09-05 14:57 ` bug#26048: " 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=877exklo5j.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).