This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/21457] sys/ucontext.h namespace
- From: "carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 29 Jun 2017 12:33:03 +0000
- Subject: [Bug libc/21457] sys/ucontext.h namespace
- Auto-submitted: auto-generated
- References: <bug-21457-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21457
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #10 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Peter Maydell from comment #8)
> The changes in this bug appear to break building QEMU with this version of
> glibc (we use "struct ucontext" rather than "ucontext_t"). Can this be
> reverted, please? I think breaking real world code for the purposes of a
> theoretical namespace cleanup is not an ideal tradeoff.
The GNU C Library does not provide backwards compatibility at the API level.
When recompiling your code you may need to fix things as existing APIs are
deprecated.
Namespace issues are real and impact applications and the names they can use
for their own variables, such work is just as importance as performance work in
the longer term.
If you need to build a new QEMU, you need to fix the new QEMU to build with the
new glibc. This is a normal part of building with a new toolchain.
There is a C++ ABI change with the change of the structure name, but analysis
of distribution binaries shows this should not be an issue, though we would
appreciate any feedback on that aspect of the change.
Please see:
https://sourceware.org/glibc/wiki/Release/2.26#Removal_of_.27struct_ucontext.27
--
You are receiving this mail because:
You are on the CC list for the bug.