From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Nieuwenhuizen Subject: Re: 11/33: gnu: glibc: Add and update patches for the Hurd. Date: Tue, 10 Mar 2020 12:28:37 +0100 Message-ID: <87sgig30uy.fsf@gnu.org> References: <20200310075832.7126.86402@vcs0.savannah.gnu.org> <20200310075846.1DA6821123@vcs0.savannah.gnu.org> <871rq0y44w.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:39137) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jBd3x-0005K3-MF for guix-devel@gnu.org; Tue, 10 Mar 2020 07:28:45 -0400 In-Reply-To: <871rq0y44w.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 10 Mar 2020 10:02:07 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org Sender: "Guix-devel" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org Ludovic Court=C3=A8s writes: >> * gnu/packages/patches/glibc-hurd-clock_t_centiseconds.patch: New fi= le. >> * gnu/packages/patches/glibc-hurd-clock_gettime_monotonic.patch: New= file. >> * gnu/local.mk (dist_patch_DATA): Update them. >> * gnu/packages/base.scm (glibc): Use two new patches. > > [...] > >> - (patches (search-patches "glibc-ldd-x86_64.patch" >> + (patches `(,@(search-patches "glibc-ldd-x86_64.patch" > ^ > Superfluous. :-) Ah yes thanks, removed. (I had a number of patches that meant to avoid triggering rebuilds -- this is a leftover. >> + "glibc-hurd-clock_t_centisecon= ds.patch" >> + "glibc-hurd-clock_gettime_mono= tonic.patch"))))) > > Nice patches! Did you submit them upstream? They are likely to be > applied quite quickly nowadays, so they could make it in glibc 2.32. > (It=E2=80=99s fine to carry them in the meantime, of course.) I "only" forward ported them, and fixed one; only to find the Debian glibc git archive just yesterday; so very similar ones are in Debian. It is unclear to me how that works, some are prefixed local-, others submitted- or unsubmitted-. I'll have to ask around. Worse, I just found what I meant to fix before with glibc-hurd-clock_gettime_monotonic.patch namely Fatal Python error: Py_Initialize: can't initialize time OSError: [Errno 1073741846] Invalid argument has somehow regressed...bah! Combining that with our make v4.1/v4.3 problem, I guess I'll need to dive into these Debian patches some more. Greetings, janneke --=20 Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar=C2=AE http://AvatarAcademy.com