public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: kevin diggs <diggskevin38@gmail.com>
Cc: Steffen Dettmer <steffen.dettmer@googlemail.com>,
	binutils@sourceware.org
Subject: Re: binutils prerequisites (recent zlib version - what else?)
Date: Tue, 26 Apr 2011 18:19:00 -0000	[thread overview]
Message-ID: <mcry62wq3jh.fsf@coign.corp.google.com> (raw)
In-Reply-To: <BANLkTinSO442Aj_mZ41F9ydzyt6+z4VGZA@mail.gmail.com> (kevin	diggs's message of "Tue, 26 Apr 2011 13:05:02 -0500")

kevin diggs <diggskevin38@gmail.com> writes:

> On Tue, Apr 26, 2011 at 11:26 AM, Ian Lance Taylor <iant@google.com> wrote:
>>
>> Unrecognized --with options are ignored.  The difference in the
>>
>> Ian
>>
> Why? Wouldn't it be better to tell the poor, confused user that they
> are configuring up the wrong tree? So that we can go RTFM and get the
> right option (or whine and complain if the desired functionality does
> not exist)?

It would be better in some cases, yes.  However, the gcc and binutils
trees are examples where there is a master configure script at the top
which invokes a range of sub-configure scripts below.  To make that
work, the master configure script needs to pass all --with and --enable
options to the sub-configure scripts.  If configure scripts reject
unrecognized options, then it would be necessary for every configure
script to recognize every option.  Since the sub-projects are maintained
by different groups of people, that is infeasible.

To avoid the problem there is, yes, an option: --enable-option-checking.
It's sort of pathetic to have an option for option checking, since most
people aren't going to be aware of it, but it's the best we have at the
moment.

Ian

  parent reply	other threads:[~2011-04-26 18:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20 12:44 Steffen Dettmer
2011-04-26 14:52 ` Steffen Dettmer
2011-04-26 16:27   ` Ian Lance Taylor
2011-04-26 16:34     ` Steffen Dettmer
2011-04-26 17:04       ` H.J. Lu
2011-04-26 18:34         ` Steffen Dettmer
2011-04-26 18:05     ` kevin diggs
2011-04-26 18:11       ` kevin diggs
2011-04-26 18:21         ` Ian Lance Taylor
2011-04-26 18:19       ` Ian Lance Taylor [this message]
2011-04-26 18:39         ` Steffen Dettmer
2011-04-26 18:44           ` Steffen Dettmer
2011-04-27  6:08         ` Ralf Wildenhues
2011-08-04 22:08 ` [PATCH] Correct zlib checks [Was: binutils prerequisites (recent zlib version - what else?)] Maciej W. Rozycki
2011-08-05  7:52   ` Paolo Bonzini

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=mcry62wq3jh.fsf@coign.corp.google.com \
    --to=iant@google.com \
    --cc=binutils@sourceware.org \
    --cc=diggskevin38@gmail.com \
    --cc=steffen.dettmer@googlemail.com \
    /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).