[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gcc-bugs
Subject:    other/2126: configure script fails with --silent option
From:       pirie () u ! washington ! edu
Date:       2001-02-28 16:41:54
[Download RAW message or body]


> 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:


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic