From: James E Wilson <wilson@specifix.com>
To: Peter O'Gorman <peter@pogma.com>
Cc: Jack Howarth <howarth@bromo.msbb.uc.edu>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org,
Geoff Keating <geoffk@apple.com>
Subject: Re: -b vs -bundle
Date: Fri, 05 Aug 2005 03:14:00 -0000 [thread overview]
Message-ID: <1123211669.31826.60.camel@aretha.corp.specifix.com> (raw)
In-Reply-To: <42F20D0D.6070200@pogma.com>
On Thu, 2005-08-04 at 05:41, Peter O'Gorman wrote:
> + trying to interpret the rest of the command line.
> + Use heuristic that all copnfiguration names must have at least
> + one dash '-'. This allows us to pass options starting with -b. */
There is a typo here copnfiguration->configuration.
There are a number of valid configurations that do not contain a hyphen,
though they are not commonly used. For instance configuring for
--target=mips will give you a mips-elf toolchain that will install a
mips-gcc executable. I think it is reasonable to discourage use of such
ambiguous target names here. It helps that -b is also not commonly
used.
However, we do need to document this restriction. In fact, if you look
at the docs for the -b option, it gives an example that will no longer
work. (It is also an obsolete configuration.) So the docs need to be
updated to mention that the machine name must contain a hyphen, and to
use a more reasonable target, like arm-elf perhaps.
While we are at it, we could perhaps fix the -V docs to mention a
realistic gcc version number too. 2.0 is a little too old to be useful.
This revised patch does appear to fix the only complaint that Geoff had
with the original patch. I think it is OK with the typo fixed and the
addition of a doc change.
--
Jim Wilson, GNU Tools Support, http://www.specifix.com
next prev parent reply other threads:[~2005-08-05 3:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-31 19:06 Jack Howarth
2005-08-01 20:28 ` Geoff Keating
2005-08-04 4:30 ` James E Wilson
2005-08-04 12:44 ` Peter O'Gorman
2005-08-05 3:14 ` James E Wilson [this message]
2005-08-05 3:57 ` Peter O'Gorman
2005-08-07 2:42 ` James E Wilson
2005-08-01 20:47 Jack Howarth
2005-08-01 20:52 ` Geoff Keating
2005-08-01 21:27 Jack Howarth
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=1123211669.31826.60.camel@aretha.corp.specifix.com \
--to=wilson@specifix.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@apple.com \
--cc=howarth@bromo.msbb.uc.edu \
--cc=peter@pogma.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).