unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
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: Sun, 23 Apr 2017 15:58:41 +0200	[thread overview]
Message-ID: <87k26bdy3y.fsf@gnu.org> (raw)
In-Reply-To: <87zif7sc88.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 23 Apr 2017 11:29:59 +0200")

Ricardo Wurmus <rekado@elephly.net> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> skribis:
>>
>>> 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
>>
>> Perhaps we don’t see the problem when running i686 code on x86_64.
>>
>>> 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.
>>
>> Could you first check if there’s a simple way to reproduce it on your
>> machine?  For example, run “guix build coreutils” or “guix build
>> coreutils --check” and see if that fails.
>>
>> If it does, you could arrange to test the patch just in this setup.
>
> Do you mean apply the patch and build on i686 or apply the patch and
> build with “--system” on my x86_64 system?
>
> On the i686 system I cannot run anything with the latest glibc, so
> building there will likely fail unless the bug is fixed.

What I mean is that if you could test the patch in any way you like ;-)
and ensure that it fixes the problem, it would be great.

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.

TIA! :-)

Ludo’.

  reply	other threads:[~2017-04-23 13:59 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 [this message]
2017-04-24 21:24       ` Ricardo Wurmus
2017-04-24 21:33         ` Ricardo Wurmus
2017-04-25 10:19         ` Ludovic Courtès
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=87k26bdy3y.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).