[ Sorry for breaking threading, am not subscribed, yaddayadda ] Stephan Bergmann wrote: > Another problem that only dawned on us recently is the following: The > OOo source includes a number of external projects that deliver C/C++ > headers that are included from other modules. To suppress warnings from > such headers, patches have been included for some of those external > projects on warnings01. However, some people build OOo in such a way > that they use system-supplied alternatives of those external projects, > so that the patches will have no effect for them. That means that > switching on "warnings are errors" can break such builds (although the > "official" OOo builds would succeed).
That's not only a problem with system libraries, but also with system compilers. People will compile the code with newer compilers than those used during testing of warnings01. Compilers with new warnings that will break the build if -Werror or equivalents are in use. Martin
