From: NightStrike <nightstrike@gmail.com>
To: "Ian Lance Taylor" <iant@google.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: top-level configure options, --help
Date: Fri, 04 Jan 2008 06:13:00 -0000 [thread overview]
Message-ID: <b609cb3b0801021330n7de05e4dm441b038192d4b5e6@mail.gmail.com> (raw)
In-Reply-To: <m3k5msyxps.fsf@localhost.localdomain>
On 02 Jan 2008 08:54:39 -0800, Ian Lance Taylor <iant@google.com> wrote:
> NightStrike <nightstrike@gmail.com> writes:
>
> > I noticed that --with-sysroot is not listed in --help for the top
> > level configure, but --with-build-sysroot is. Is that on purpose?
> > Should the former not be used at all in place of the latter?
>
> This is an unfortunate artifact of autoconf --help handling with
> recursive configure scripts. You'll see both mentioned in the output
> of gcc/configure --help. --with-build-sysroot needs to be handled at
> the top level in order to pass down the --sysroot option when
> compiling libraries; therefore, it appears in the top level --help
> output. --with-sysroot does not need to be handled at the top level;
> therefore, it does not appear in the top level --help output.
If that's the case, there must be more options as well that are not
present in top level's --help that really are options that the user
would actually use. I would think that a simple AS_HELP_STRING macro
in the top level configure would accomplish this. That, or a blank
ARG_WITH macro.. something like:
AC_ARG_WITH([sysroot],
[AS_HELP_STRING([--with-sysroot],
[Sets the sysroot])],
[],
[])
You could list the option in the top level configure, but give it no
action. This is a benefit to the user, so that the top level
configure --help contains all the options that a user would use.
next prev parent reply other threads:[~2008-01-02 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-29 20:47 NightStrike
2008-01-04 2:18 ` Ian Lance Taylor
2008-01-04 6:13 ` NightStrike [this message]
2008-01-07 14:14 ` Brian Dessent
2008-01-07 14:25 ` NightStrike
2008-01-07 22:27 ` Brian Dessent
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=b609cb3b0801021330n7de05e4dm441b038192d4b5e6@mail.gmail.com \
--to=nightstrike@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.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).