From: Giovanni Biscuolo <g@xelera.eu>
To: "Ricardo Wurmus" <rekado@elephly.net>, "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: glibc 2.29 needs Python
Date: Thu, 30 May 2019 14:46:35 +0200 [thread overview]
Message-ID: <8736kw155g.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <87tvdcji38.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 952 bytes --]
Ricardo Wurmus <rekado@elephly.net> writes:
>> I started looking at what it would take to upgrade glibc to 2.29 on
>> ‘core-updates’. Bad news: it depends on Python.
>
> I had to check the date. This is for real?
It's for real:
--8<---------------cut here---------------start------------->8---
Changes to build and runtime requirements:
* Python 3.4 or later is required to build the GNU C Library.
--8<---------------cut here---------------end--------------->8---
https://sourceware.org/ml/libc-announce/2019/msg00000.html
AFAIU the relevant patch is
https://sourceware.org/git/?p=glibc.git;a=commit;h=c6982f7efc1c70fe2d6160a87ee44d871ac85ab0
Before that commit «Python is (was) required to build the GNU C Library
manual and to run some tests.» (and AFAIU tests was skipped if Python
was not available in the build environment)
[...]
Viva Guix! Gio'.
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-05-30 12:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 10:39 glibc 2.29 needs Python Ludovic Courtès
2019-05-30 11:29 ` Ricardo Wurmus
2019-05-30 12:46 ` Giovanni Biscuolo [this message]
2019-05-31 22:13 ` Ludovic Courtès
2019-06-01 8:48 ` Jan Nieuwenhuizen
2019-06-01 12:04 ` ng0
2019-06-01 16:48 ` Ricardo Wurmus
2019-06-20 14:09 ` Ricardo Wurmus
2019-06-20 15:06 ` Danny Milosavljevic
2019-06-20 15:25 ` Ricardo Wurmus
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=8736kw155g.fsf@roquette.mug.biscuolo.net \
--to=g@xelera.eu \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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.