This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH v2] Remove union wait
- From: Florian Weimer <fweimer at redhat dot com>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: Andreas Schwab <schwab at suse dot de>, "Carlos O'Donell" <carlos at redhat dot com>, libc-alpha at sourceware dot org
- Date: Tue, 12 Apr 2016 13:37:57 +0200
- Subject: Re: [PATCH v2] Remove union wait
- Authentication-results: sourceware.org; auth=none
- References: <56BE07C8 dot 40205 at redhat dot com> <20160307225511 dot 093E92C3BF5 at topped-with-meat dot com> <56DEA20E dot 3040907 at redhat dot com> <56FBBCAF dot 7090806 at redhat dot com> <20160330223228 dot 6A7382C3C54 at topped-with-meat dot com> <56FC5A6C dot 8090408 at redhat dot com> <mvmy48z5dc2 dot fsf at hawking dot suse dot de> <5707AA6C dot 1080800 at redhat dot com> <mvmegacwm33 dot fsf at hawking dot suse dot de> <570BC36A dot 1050603 at redhat dot com> <20160411215550 dot 692942C3AC8 at topped-with-meat dot com>
On 04/11/2016 11:55 PM, Roland McGrath wrote:
But I will point out that the claim that the deprecation warnings are
just as bad as outright removal is not really right. Packagers or
system-builders or whoever can add -Wno-error=deprecated to the
compilation flags for a particular package via configure, or for an
entire package-building system in that system's configuration for
building all packages (a la redhat-rpm-config), etc.
There are so many build systems out there. Figuring out how to disable
-Werror is often more complicated than patching sources to get rid of
the warning (especially if there are few places where the warning
triggers, and the required change is straightforward). Some projects do
this deliberately to prevent warnings from accumulating.
At scale (for an entire distribution which has just rebased glibc),
there is sometimes little difference between the two approaches to get
rid of the deprecation warning.