From mboxrd@z Thu Jan  1 00:00:00 1970
From: pirie@u.washington.edu
To: gcc-gnats@gcc.gnu.org
Subject: other/2126: configure script fails with --silent option
Date: Sun, 01 Apr 2001 00:00:00 -0000
Message-id: <20010228164154.20445.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-q1/msg01823.html
List-Id: <gcc-prs.sourceware.org>

>Number:         2126
>Category:       other
>Synopsis:       configure script fails with --silent option
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Wed Feb 28 08:46:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Pirie Hart
>Release:        2.95.2
>Organization:
>Environment:

>Description:
Two command line options, --silent and --site=SITE are supported.  

Code on line 193 attempts to identify options that require, but are missing, values.  --site requires a value; --silent does not.  --si* matches both, so --silent is rejected as not having a required value.  Changing the code on line 193 from '--si*' to '--sit*' will trap --site with no value but allow --silent to pass.

Current workaround is to either patch the configure script before running it, or use the --quiet option.
>How-To-Repeat:
>>From gcc_objdir, type
     ../gcc-2.95.2/configure --silent
>Fix:
In the gcc-2.95.2/configure script, line 193,
     " ... | --si* | ... "
should be changed to
     " ... | --sit* | ... ".  

>Release-Note:
>Audit-Trail:
>Unformatted: