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. > > But the build (of the software or the tests) could fail due to a > > feature that should have been disabled by an error detected with > > -Werror at configure time. > > I can't think of any example, can you please explain? See above. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org