This is the mail archive of the
mailing list for the glibc project.
[Bug build/20621] glibc 2.24 fails to compile on x86_64 with "operand type mismatch" in fpu/e_expl.S
- From: "carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 22 Sep 2016 20:39:14 +0000
- Subject: [Bug build/20621] glibc 2.24 fails to compile on x86_64 with "operand type mismatch" in fpu/e_expl.S
- Auto-submitted: auto-generated
- References: <firstname.lastname@example.org/bugzilla/>
--- Comment #13 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Michael Tremer from comment #12)
> (In reply to email@example.com from comment #11)
> > On Thu, 22 Sep 2016, michael.tremer at ipfire dot org wrote:
> > I'm not sure "should be supported" is meaningful for undocumented
> > features. Such combinations of features will inevitably bitrot unless
> > there are people taking an active role in keeping them working during
> > development, including sending patches to fix issues that arise.
> Fedora is using BIND_NOW, too:
They are, but they haven't thought through the full consequences of this
action. At a high level the project wants BIND_NOW for everything, but there
are quite a few wrinkles to iron out regarding BIND_NOW.
You are receiving this mail because:
You are on the CC list for the bug.