This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug math/22146] C++ build issue with float128 on x86_64
- From: "gabriel at inconstante dot eti.br" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Mon, 25 Sep 2017 12:45:49 +0000
- Subject: [Bug math/22146] C++ build issue with float128 on x86_64
- Auto-submitted: auto-generated
- References: <bug-22146-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22146
Gabriel F. T. Gomes <gabriel at inconstante dot eti.br> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |siddhesh at sourceware dot org
--- Comment #17 from Gabriel F. T. Gomes <gabriel at inconstante dot eti.br> ---
(In reply to romain.naour from comment #16)
>
> Do you plan to release glibc 2.26.1 soon ?
> It would help me to update to glibc 2.26.x in Buildroot since I need to
> backport (at least) patches for bug 21930 and this one.
Each branch in glibc is maintained by a release manager [1] (for glibc 2.26,
that would be Siddhesh (now in CC)). We could ask him what are the plans for
further tagging, if any.
Romain, let me ask you this in advance... In Buildroot, can you fetch the
components from a particular revision in their VCS, meaning you could fetch
glibc from a commit ID that contains this backport (i.e.: commit ID
d37c951fde57 or newer)?
[1] https://sourceware.org/glibc/wiki/Release#General_policy (not written in
stone, but provides some insight into the branch/tag policies)
--
You are receiving this mail because:
You are on the CC list for the bug.