From: ludo@gnu.org (Ludovic Courtès)
To: Marius Bakke <mbakke@fastmail.com>
Cc: 29406@debbugs.gnu.org
Subject: [bug#29406] [PATCH core-updates]: Add selected upstream fixes for glibc 2.26.
Date: Thu, 23 Nov 2017 16:42:22 +0100 [thread overview]
Message-ID: <874lplvw69.fsf@gnu.org> (raw)
In-Reply-To: <87mv3eove6.fsf@fastmail.com> (Marius Bakke's message of "Wed, 22 Nov 2017 22:28:49 +0100")
Hello!
Marius Bakke <mbakke@fastmail.com> skribis:
> I discovered that 'icu4c' failed to build for x86_64 on 'core-updates'.
> After some investigation, it turns out to be a problem with <math.h> in
> C++ mode, due to its usage of C-only builtins (in the 2.26 release).
[...]
> So I wonder if we should simply pick everything from this branch,
> instead of only the few that fixes immediately visible problems.
> Thoughts?
Cherry-picking like you did sounds reasonable to me.
That said, as discussed on IRC, I think that it’s up to upstream to tell
us what code we should be building, and a simple way to do that is by
making a bug-fix release.
> From 7121dc7ed24e97080154794fb14ae4078a3451f7 Mon Sep 17 00:00:00 2001
> From: Marius Bakke <mbakke@fastmail.com>
> Date: Wed, 22 Nov 2017 22:26:31 +0100
> Subject: [PATCH] gnu: glibc: Add selected fixes from upstream stable branch.
>
> This backports a small subset of
> <https://sourceware.org/git/?p=glibc.git;a=shortlog;h=refs/heads/release/2.26/master>.
>
> * gnu/packages/patches/glibc-2.26-cpp-fixes.patch,
> gnu/packages/patches/glibc-2.26-ifunc-resolver-longjmp.patch,
> gnu/packages/patches/glibc-2.26-resolver-fixes.patch: New files.
> * gnu/local.mk (dist_patch_DATA): Register them.
> * gnu/packages/base.scm (glibc/linux)[source](patches): Use them.
Great that you created one patch for each category of bug.
LGTM!
After applying, you can restart an evaluation of ‘core-updates’.
Thanks,
Ludo’.
prev parent reply other threads:[~2017-11-23 15:43 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
2017-11-28 18:26 ` Leo Famulari
2017-11-23 15:42 ` Ludovic Courtès [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
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=874lplvw69.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=29406@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
/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).