This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/21457] sys/ucontext.h namespace


https://sourceware.org/bugzilla/show_bug.cgi?id=21457

--- Comment #15 from Peter Maydell <peter.maydell at linaro dot org> ---
The issue is with other projects whose release cycles aren't necessarily
aligned with glibc's. We can certainly update QEMU now, but that means that
until we do our next QEMU release, people running new glibc will have no
released version of QEMU that will build on their system. If glibc has a
deprecation period before actually removing things, then we get advance notice
that we need to make a fix, and so we're likely to be able to release a fixed
QEMU before the glibc is released which actually removes the feature we were
using.

If you need new compiler features to be able to implement this for some kinds
of deprecation you can talk to the gcc folk :-)

Incidentally, I notice that the getcontext(3) manpage for Linux describes
"struct ucontext" -- does that need updating?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]