From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 26497@debbugs.gnu.org
Subject: bug#26497: glibc 2.25 broken on i686
Date: Tue, 25 Apr 2017 12:19:15 +0200 [thread overview]
Message-ID: <87bmrkdc2k.fsf@gnu.org> (raw)
In-Reply-To: <87k269sdm6.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 24 Apr 2017 23:24:33 +0200")
Hello!
Ricardo Wurmus <rekado@elephly.net> skribis:
> I applied the following patch to my i686 netbook and waited a day for
> coreutils and procps to be built with the new glibc. I cannot reproduce
> any crashes with these packages, so this seems to be fine.
>
>> Then we soon apply the patch conditionally on glibc (like I did for the
>> Coreutils patch for ARM) ASAP so that Hydra has time to rebuild the i686
>> world.
>
> The attached patch is for core-updates, but I could also try to make it
> apply conditionally for i686.
Yes, that would be great.
> From 2b2f1d4947e2198f7011b00a496be078f6a924fd Mon Sep 17 00:00:00 2001
> From: Ricardo Wurmus <rekado@elephly.net>
> 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.
Perfect, thank you for taking care of it!
Ludo’.
next prev parent reply other threads:[~2017-04-25 10:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 11:47 bug#26497: glibc 2.25 broken on i686 Ricardo Wurmus
2017-04-14 12:56 ` Ludovic Courtès
2017-04-23 9:29 ` Ricardo Wurmus
2017-04-23 13:58 ` Ludovic Courtès
2017-04-24 21:24 ` Ricardo Wurmus
2017-04-24 21:33 ` Ricardo Wurmus
2017-04-25 10:19 ` Ludovic Courtès [this message]
2017-05-05 17:32 ` 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=87bmrkdc2k.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=26497@debbugs.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).