This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug build/20621] glibc 2.27 fails to compile on x86_64 with "operand type mismatch" in fpu/e_expl.S
- From: "michael.tremer at ipfire dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 22 Sep 2016 15:27:33 +0000
- Subject: [Bug build/20621] glibc 2.27 fails to compile on x86_64 with "operand type mismatch" in fpu/e_expl.S
- Auto-submitted: auto-generated
- References: <bug-20621-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20621
Michael Tremer <michael.tremer at ipfire dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hjl.tools at gmail dot com
--- Comment #10 from Michael Tremer <michael.tremer at ipfire dot org> ---
(In reply to joseph@codesourcery.com from comment #9)
> Maybe no-one has ever tried the combination of --enable-bind-now (an
> undocumented configure option) with a default-PIE compiler before (or at
> least, no-one regularly tests such a combination in development). We
> could do with more buildbot instances testing unusual configurations (of
> course, they need people who care about those configurations monitoring
> them and addressing build issues when they arise).
So am I correct when I take this as this configuration should be supported but
is currently just broken?
It compiles through without --with-bind-now, so this commit is causing the
problem: 6901def689b5c77465d34f07822989ec67e80c1e
I have absolutely no idea how to fix this despite reverting the commit. So far
the result would only be bigger binaries.
--
You are receiving this mail because:
You are on the CC list for the bug.