emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#26497: closed (glibc 2.25 broken on i686)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#26497: closed (glibc 2.25 broken on i686)
Date: Fri, 05 May 2017 17:33:01 +0000

Your message dated Fri, 05 May 2017 19:32:34 +0200
with message-id <address@hidden>
and subject line Re: bug#26497: glibc 2.25 broken on i686
has caused the debbugs.gnu.org bug report #26497,
regarding glibc 2.25 broken on i686
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
26497: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=26497
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: glibc 2.25 broken on i686 Date: Fri, 14 Apr 2017 13:47:59 +0200 User-agent: mu4e 0.9.18; emacs 25.1.1
Guix on i686 is broken since the update to glibc 2.25.  There are
seemingly random segfaults all over the place on my server.

Ludo posted this upstream discussion:

    https://sourceware.org/bugzilla/show_bug.cgi?id=21182

I could test the patch on my i686 system, but it would take much too
long for me to build the system from source on my machines.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net




--- End Message ---
--- Begin Message --- Subject: Re: bug#26497: glibc 2.25 broken on i686 Date: Fri, 05 May 2017 19:32:34 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux)
Ricardo Wurmus <address@hidden> skribis:

>>From 2b2f1d4947e2198f7011b00a496be078f6a924fd Mon Sep 17 00:00:00 2001
> From: Ricardo Wurmus <address@hidden>
> Date: Mon, 24 Apr 2017 23:15:41 +0200
> Subject: [PATCH] gnu: glibc/linux: Fix segfaults on i686.
>
> * gnu/packages/patches/glibc-memchr-overflow-i686.patch: New file.
> * gnu/local.mk (dist_patch_DATA): Add it.
> * gnu/packages/base.scm (glibc/linux)[source]: Add patch.

This was pushed as b2fd8f63679aa4f244c36fdca62f23c00b8eded9; closing.

Ludo’.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]