public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Barada <pbarada@mail.wm.sps.mot.com>
To: aoliva@redhat.com
Cc: lucier@math.purdue.edu, gcc@gcc.gnu.org
Subject: Re: 3.0.4 builds for solaris 2.7 and 2.8
Date: Mon, 25 Feb 2002 07:39:00 -0000	[thread overview]
Message-ID: <200202251533.g1PFXeu17665@hyper.wm.sps.mot.com> (raw)
In-Reply-To: <orvgcozv3i.fsf@free.redhat.lsd.ic.unicamp.br> (message from Alexandre Oliva on 23 Feb 2002 01:21:37 -0300)


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

If you're asking for ideas, howsa about this one :-)

Have the top-level configuration script build a file that contains
a list of the configuration option passed in, one per line, and the
sub-packages configure script removes from the list those options that
it understands.  At the end of all the sub-package configurations, if
there is anything left in the list then its either unknown or mispelled.
Of course the top-level configuration script would any that it
undrestands.

-- 
Peter Barada                                   Peter.Barada@motorola.com
Wizard                                         781-852-2768 (direct)
WaveMark Solutions(wholly owned by Motorola)   781-270-0193 (fax)

  parent reply	other threads:[~2002-02-25 15:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-22 20:05 lucier
2002-02-22 20:31 ` Alexandre Oliva
2002-02-22 20:43   ` Brad Lucier
2002-02-22 20:47     ` Alexandre Oliva
2002-02-22 21:01       ` Brad Lucier
2002-02-22 21:49         ` Alexandre Oliva
2002-02-24  2:26   ` Fergus Henderson
2002-02-24  4:14     ` Alexandre Oliva
2002-02-24  6:21       ` Fergus Henderson
2002-02-24 19:23       ` Phil Edwards
2002-02-24 11:42   ` Mark Mitchell
2002-02-24 13:28     ` Alexandre Oliva
2002-02-25  7:39   ` Peter Barada [this message]
2002-02-25  8:54     ` Alexandre Oliva
  -- strict thread matches above, loose matches on Subject: below --
2002-02-22 15:42 George.R.Goffe
2002-02-22 16:28 ` Alexandre Oliva
2002-02-22 17:26 ` Janis Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200202251533.g1PFXeu17665@hyper.wm.sps.mot.com \
    --to=pbarada@mail.wm.sps.mot.com \
    --cc=aoliva@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=lucier@math.purdue.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).