>Number: 3958 >Category: config >Synopsis: configure silently ignores "--enable-XXX" options where XXX is >unknown >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Wed Feb 24 04:10:00 PST 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.4 >Environment: Solaris 2.6 >Description: If I mistype:
./configure --enable-module=mod-speling as: ./configure --enable-modules=mod-speling I get no error, but apache builds without mod-speling. In fact --enable-XXX is ignored if XXX is unknown. I think this deserves an error message to avoid the pitfall of mis-spelling a --enable-XXX option and having it ignored. There are similar issues for --disable-XXX. >How-To-Repeat: ./configure --enable-modules=mod-speling >Fix: Add a "*)" catch-all to report this error at lines 711 and 769 of configure. >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]
