Re: Latest snapshot won't build with --enable-libstdcxx-v3

[Theodore Papadopoulo <Theodore dot Papadopoulo at sophia dot inria dot fr>]

jbuck@racerx.synopsys.com said:
> I wasn't the person who decided to put in -Werror, but I think it is a
> very good idea for libstdc++ to use it.

> 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 think that everyone agrees that it is a good idea. Unfortunately, 
it sometimes prevents people (I'm among them) to compile libstc++-v3
because of bugs in their system include file (which sadly is a not so
old glibc) which is bad, and for which we do not have any workaround
currently.

That's too bad, but to encourage more people test the new library it 
was better to remove Werror. It is still there when using
--enable-maintainer-mode IIRC.

But my question was another one.... Certainly I have not been clear 
enough.

I was wondering what was the rationale behind redirecting the 
compiler messages to /dev/null which is exactly the opposite of the 
philosophy exposed above, ie expose the developers  to the messages 
as much as possible!!!

	Theo.

--------------------------------------------------------------------
Theodore Papadopoulo
Email: Theodore.Papadopoulo@sophia.inria.fr Tel: (33) 04 92 38 76 01
 --------------------------------------------------------------------