This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
other/2126: configure script fails with --silent option
- To: gcc-gnats at gcc dot gnu dot org
- Subject: other/2126: configure script fails with --silent option
- From: pirie at u dot washington dot edu
- Date: 28 Feb 2001 16:41:54 -0000
- Reply-To: pirie at u dot washington dot edu
>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: