From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 29406-done@debbugs.gnu.org
Subject: [bug#29406] [PATCH core-updates]: Add selected upstream fixes for glibc 2.26.
Date: Wed, 29 Nov 2017 17:40:17 +0100 [thread overview]
Message-ID: <87y3mpqbri.fsf@gnu.org> (raw)
In-Reply-To: <20171128214204.GC16214@jasmine.lan> (Leo Famulari's message of "Tue, 28 Nov 2017 16:42:04 -0500")
Leo Famulari <leo@famulari.name> skribis:
> On Tue, Nov 28, 2017 at 10:02:04PM +0100, Ludovic Courtès wrote:
>> Marius Bakke <mbakke@fastmail.com> skribis:
>>
>> > Typical: The 2.26 branch just got 10 new commits that look important:
>> >
>> > https://sourceware.org/git/?p=glibc.git;a=shortlog;h=refs/heads/release/2.26/master
>> >
>> > Especially the malloc() fixes. Should we pick them while we still have
>> > time, or update the snapshot?
>>
>> Your call! :-)
>>
>> Maybe we can focus on building more on the branch, and revisit this
>> issue when we’re ready to build the whole branch. (Or are we ready
>> yet?)
>>
>> WDYT?
>
> I think there's not much to do without at least some of the glibc
> patches, because icu4c fails to build.
The glibc tarball I uploaded does fix icu4c, doesn’t it?
Anyway I’m happy to update another tarball when you want!
Ludo’.
next prev parent reply other threads:[~2017-11-29 16:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 21:28 [bug#29406] [PATCH core-updates]: Add selected upstream fixes for glibc 2.26 Marius Bakke
2017-11-23 14:57 ` Leo Famulari
2017-11-24 1:12 ` Marius Bakke
2017-11-24 3:08 ` Marius Bakke
2017-11-27 21:30 ` Leo Famulari
2017-11-28 1:42 ` Marius Bakke
2017-11-28 10:45 ` Ludovic Courtès
2017-11-28 12:54 ` Marius Bakke
2017-11-28 16:03 ` bug#29406: " Ludovic Courtès
2017-11-28 17:16 ` [bug#29406] " Marius Bakke
2017-11-28 21:02 ` Ludovic Courtès
2017-11-28 21:42 ` Leo Famulari
2017-11-29 16:40 ` Ludovic Courtès [this message]
2017-11-28 18:26 ` Leo Famulari
2017-11-23 15:42 ` 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=87y3mpqbri.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=29406-done@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).