From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 26497@debbugs.gnu.org
Subject: bug#26497: glibc 2.25 broken on i686
Date: Sun, 23 Apr 2017 11:29:59 +0200 [thread overview]
Message-ID: <87zif7sc88.fsf@elephly.net> (raw)
In-Reply-To: <87d1cfdu6c.fsf@gnu.org>
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.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-04-23 9:31 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zif7sc88.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=26497@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.