This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Latest snapshot won't build with --enable-libstdcxx-v3
- To: jbuck at racerx dot synopsys dot com
- Subject: Re: Latest snapshot won't build with --enable-libstdcxx-v3
- From: Marc Espie <espie at quatramaran dot ens dot fr>
- Date: Fri, 22 Sep 2000 02:39:42 +0200
- Cc: gcc at gcc dot gnu dot org
- Organization: Ecole Normale Superieure (quatramaran)
- References: <200009200838.e8K8ctO28043@mururoa.inria.fr>
In article <200009201530.IAA14094@racerx.synopsys.com> you write:
>Warnings produced by the inclusion of system library header files are not
>acceptable, because it means that no user of the library can use flags
>like -Wall without being distracted by warnings from the system library.
>(Old-time Cygnoids are sure to remember how I always used to beat them
>up for this - libg++ used to always generate piles of warnings, I'd send
>lots of little patches to fix them, and then the next release would
>put them all back again).
>Putting in -Werror forces the developers to produce warning-free code.
I'd concur.
Not only that, but some people routinely compile some critical code with
a large list of warnings, plus -Werror... (the OpenBSD kernel, for instance).
so yes, having warnings in header code is a complete no-no.