From: Ricardo Wurmus <rekado@elephly.net>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: glibc/linux: Fix runtime crashes on i686 systems.
Date: Sun, 30 Apr 2017 11:00:34 +0200 [thread overview]
Message-ID: <87mvayqngt.fsf@elephly.net> (raw)
In-Reply-To: <87bmrewbrp.fsf@netris.org>
Hi Mark,
> rekado@elephly.net (Ricardo Wurmus) writes:
>
>> rekado pushed a commit to branch master
>> in repository guix.
>>
>> commit b2fd8f63679aa4f244c36fdca62f23c00b8eded9
>> Author: Ricardo Wurmus <rekado@elephly.net>
>> Date: Wed Apr 26 13:03:48 2017 +0200
>>
>> gnu: glibc/linux: Fix runtime crashes on i686 systems.
>>
>> * gnu/packages/patches/glibc-memchr-overflow-i686.patch: New file.
>> * gnu/local.mk (dist_patch_DATA): Add it.
>> * gnu/packages/commencement.scm (glibc-final-with-bootstrap-bash)[native-inputs]:
>> Add the patch conditionally for i686 systems.
>> * gnu/packages/base.scm (glibc/linux)[native-inputs]: Add the patch
>> conditionally for i686 systems.
>> [arguments]: Apply the patch conditionally on i686 systems.
>
> Thanks very much for this. I noticed a minor issue with this patch: […]
Thanks for your comments. You’re right.
I’ve also noticed that something’s wrong with this patch, even though it
appeared to work fine when cross-building glibc on my x86_64 machine.
I’ll fix these issues shortly.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
prev parent reply other threads:[~2017-04-30 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170429213253.6080.61219@vcs0.savannah.gnu.org>
[not found] ` <20170429213255.095472109D@vcs0.savannah.gnu.org>
2017-04-30 8:16 ` 01/01: gnu: glibc/linux: Fix runtime crashes on i686 systems Mark H Weaver
2017-04-30 9:00 ` Ricardo Wurmus [this message]
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=87mvayqngt.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.