This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Propose requiring Python 3.4 or later for building glibc.
- From: Adam Conrad <adconrad at 0c3 dot net>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>, "Dmitry V. Levin" <ldv at altlinux dot org>, Allan McRae <allan at archlinux dot org>, Aurelien Jarno <aurelien at aurel32 dot net>, debian-glibc at lists dot debian dot org, Siddhesh Poyarekar <siddhesh at gotplt dot org>, Florian Weimer <fweimer at redhat dot com>, "Andreas K. Huettel" <dilfridge at gentoo dot org>, Sergei Trofimovich <slyfox at gentoo dot org>, Khem Raj <raj dot khem at gmail dot com>, Andreas Schwab <schwab at suse dot de>, Tulio Magno Quites Machado Filho <tuliom at linux dot vnet dot ibm dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>, Jeff Law <law at redhat dot com>
- Date: Fri, 19 Oct 2018 13:59:35 +0000
- Subject: Re: Propose requiring Python 3.4 or later for building glibc.
- References: <258837a9-50bf-d2b3-950a-c28e5b411e8f@redhat.com>
On Fri, Oct 19, 2018 at 09:47:14AM -0400, Carlos O'Donell wrote:
>
> Adam,
>
> Any input from Ubuntu?
I think the more tools you involve in any bootstrap process, the more
painful you're going to make it for people bringing up a new arch.
Python isn't exactly lightweight (though there are ways to build just
stdlib and not much else), and intertwining a python bootstrap with
the already tiresome gcc/glibc/etc bootstraps won't fill me with warm
fuzzies.
With the above objection registered, I'll note that for both Debian
and Ubuntu, python3.4 is sufficiently ancient that we'll have no issues
meeting the actual requirement, and for most cases, we shouldn't really
see an issue with the above "oh noes, more bootstrap bits", cause we
can reliably cross bootstrap and ignore the whole issue.
... Adam