From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30507 invoked by alias); 24 Feb 2002 10:15:48 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 30363 invoked from network); 24 Feb 2002 10:15:44 -0000 Received: from unknown (HELO mulga.cs.mu.OZ.AU) (128.250.1.22) by sources.redhat.com with SMTP; 24 Feb 2002 10:15:44 -0000 Received: from murlibobo.cs.mu.OZ.AU (murlibobo.cs.mu.OZ.AU [128.250.37.153]) by mulga.cs.mu.OZ.AU with ESMTP id VAA08952; Sun, 24 Feb 2002 21:15:41 +1100 (EST) Received: (from fjh@localhost) by murlibobo.cs.mu.OZ.AU (8.11.3/8.11.3) id g1OAFda82798; Sun, 24 Feb 2002 21:15:39 +1100 (EST) Date: Sun, 24 Feb 2002 02:26:00 -0000 From: Fergus Henderson To: Alexandre Oliva Cc: lucier@math.purdue.edu, gcc@gcc.gnu.org Subject: Re: 3.0.4 builds for solaris 2.7 and 2.8 Message-ID: <20020224211539.A75055@murlibobo.cs.mu.OZ.AU> References: <200202230356.g1N3uDk27184@banach.math.purdue.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from aoliva@redhat.com on Sat, Feb 23, 2002 at 01:21:37AM -0300 X-SW-Source: 2002-02/txt/msg01409.txt.bz2 On 23-Feb-2002, Alexandre Oliva wrote: > On Feb 23, 2002, lucier@math.purdue.edu wrote: > > > I've reported before being bitten by misspelling configure options, > > and configure does not report an error. > > So which of the configure scripts do you suggest to look for unknown > flags and report them? > > Remember that it can't be the top-level configure because it's used to > build a number of different sub-packages, each of which has its own > set of configure options that keep changing, and it can't be any of > the sub-packages' configure scripts because those shouldn't have to > know about each other :-) Obviously the different configure scripts should cooperate. For example, one way to achieve this would be for the configure scripts to accept a new option `--list-supported-options', which would cause the configure script to just echo the supported --with-* and --enable-* option names. The top-level configure script could then invoke all the subdirectory configure scripts with --list-supported-options to figure out which options were supported by the subdirectory configure scripts, and could then issue an error or warning message for options which are not supported. -- Fergus Henderson | "I have always known that the pursuit The University of Melbourne | of excellence is a lethal habit" WWW: | -- the last words of T. S. Garp.