From: Leo Famulari <leo@famulari.name>
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 09:57:02 -0500 [thread overview]
Message-ID: <20171123145702.GA5794@jasmine.lan> (raw)
In-Reply-To: <87mv3eove6.fsf@fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]
On Wed, Nov 22, 2017 at 10:28:49PM +0100, Marius Bakke wrote:
> Hello!
>
> 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).
>
> Here are the relevant bug reports I've found so far by digging through
> the "release/2.26/master" branch, aka "2.26 stable"[0]:
>
> <https://sourceware.org/bugzilla/show_bug.cgi?id=21930>
> <https://sourceware.org/bugzilla/show_bug.cgi?id=22235>
> <https://sourceware.org/bugzilla/show_bug.cgi?id=22146>
> <https://sourceware.org/bugzilla/show_bug.cgi?id=22296>
>
> The attached patch includes the fixes from those bugs, as well as a
> couple of others that looked important. However it's still a very small
> subset of the 2.26 post-release fixes.
>
> I've read through _most_ of the commits and around half of them look
> important enough to pick "unconditionally". The other half I mainly
> lack the context or skills to assess.
>
> So I wonder if we should simply pick everything from this branch,
> instead of only the few that fixes immediately visible problems.
> Thoughts?
Based on this discussion [0], I think we should take the whole branch.
It sounds like commits on the release branches are considered important
bug fixes and "stable".
There was talk of a mid-October 2.26.1 release, but that didn't happen,
as we know.
Are you able to prepare a patch, Marius? If not, I can do it later
tonight.
[0]
https://sourceware.org/ml/libc-alpha/2017-09/msg01134.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-11-23 14:58 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 [this message]
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
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=20171123145702.GA5794@jasmine.lan \
--to=leo@famulari.name \
--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 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.