From: Brad Lucier <lucier@math.purdue.edu>
To: aoliva@redhat.com (Alexandre Oliva)
Cc: lucier@math.purdue.edu (Brad Lucier), gcc@gcc.gnu.org
Subject: Re: 3.0.4 builds for solaris 2.7 and 2.8
Date: Fri, 22 Feb 2002 21:01:00 -0000 [thread overview]
Message-ID: <200202230501.g1N511F08480@banach.math.purdue.edu> (raw)
In-Reply-To: <orn0y0ztza.fsf@free.redhat.lsd.ic.unicamp.br> from "Alexandre Oliva" at Feb 23, 2002 01:45:45 AM
>
> On Feb 23, 2002, Brad Lucier <lucier@math.purdue.edu> wrote:
>
> > OK, how about a warning from the top-level configure for options it
> > can't recognize?
>
> It would be a maintenance burden to whoever modifies any of the
> sub-packages' set of supported options.
I meant that the top-level configure would be allowed to give a warning about a
valid subconfigure option.
> However, such patch wouldn't life very long, since we have a volunteer
> autoconfiscating the top-level configure script.
OK, does that mean I should stop discussing this, that it just won't be
done?
Brad
next prev parent reply other threads:[~2002-02-23 5:01 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 [this message]
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
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=200202230501.g1N511F08480@banach.math.purdue.edu \
--to=lucier@math.purdue.edu \
--cc=aoliva@redhat.com \
--cc=gcc@gcc.gnu.org \
/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).