Hi, > > Actually, one solution that would be even better IMHO would be to be > > able to turn this kind of warnings into errors that would make the > > configue script fail, i.e. not produce the files it normally produces > > from the .in files. Is this possible ? Does it make sense to you guys ? > > Yes. Here's the actual commit that implemented this all: > http://git.sv.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=2d75db Thanks! > Note in particular the addition of --enable-option-checking=fatal as a > ./configure argument. We can't make it fatal by default, because that > would violate GNU Coding Standards, but there is nothing that says that > you can't add a site.config file to make it fatal by default on your > machine. Understood. Also, is there a possibility to make it fatal on a project base ? Can the input file given to autoconf specify that for the particular project it comes with unrecognized configure options must lead to a fatalerror ? Thanks, Sébastien. _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
