./configure should error out on unknown options
Misspelled options, unknown options etc should cause configure to report an error.
#1 Updated by Will Metcalf almost 7 years ago
Seems there is no clean way to do this.
"Because the packages generally support different --with-package and --enable-feature options, the GNU Coding Standards say they must accept unrecognized options without halting"
Seems that because we are including libhtp via AC_CONFIG_SUBDIRS() we no longer even get warnings. *sigh