On Fri, Jan 10, 2014 at 03:32:12AM +0100, Vincent Lefevre wrote: > On 2014-01-09 09:04:02 -0800, Ben Pfaff wrote: > > On Thu, Jan 09, 2014 at 01:30:25PM +0100, Vincent Lefevre wrote: > > > Some configure tests *must* be done with the same options as the > > > compilation, so that some features in the program or the tests can be > > > disabled (via the preprocessor) if they are not supported due to the > > > use of -Werror. > > > > What's an example? > > Building MPFR trunk succeeds with > > $ ./configure CC=gcc-snapshot CFLAGS="-Wall -pedantic" > $ make > > and > > $ ./configure CC=gcc-snapshot CFLAGS="-Wall -pedantic -Werror" > $ make > > but fails with: > > $ ./configure --enable-Werror CC=gcc-snapshot CFLAGS="-Wall -pedantic" > $ make > > Threading support is checked at configure time. It is not supported > with "-pedantic -Werror" (due to use of extensions). If -Werror is > used at build time but not at configure time, the configure script > will detect that threading is supported (due to the missing -Werror), > though actually it isn't, so that the build fails.
So threading is supported with -pedantic but yields warnings? Then I'd want the build to fail with -Werror, exactly so that I can fix the warnings. I don't see a problem here. In my opinion, -Werror is a developer tool, not a mode for building. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
