From: Andreas Schwab <schwab@suse.de>
To: Simon Richter <Simon.Richter@hogyros.de>
Cc: binutils@sourceware.org
Subject: Re: RFC: consolidate ARM config for BFD
Date: Tue, 22 Mar 2005 04:21:00 -0000 [thread overview]
Message-ID: <je1xa85vte.fsf@sykes.suse.de> (raw)
In-Reply-To: <423F6BCF.1010703@hogyros.de> (Simon Richter's message of "Tue, 22 Mar 2005 01:50:23 +0100")
Simon Richter <Simon.Richter@hogyros.de> writes:
> case $targ in
> + nto*arm*)
> + echo "*** Please use one of the arm*-*-nto* targets"
> + exit 1
> + ;;
> +esac
This should not be necessary, config.sub wouldn't recognize anything
matching nto*arm* anyway.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, MaxfeldstraÃe 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2005-03-22 1:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 0:37 Simon Richter
2005-03-21 0:45 ` Simon Richter
2005-03-21 0:49 ` Paul Brook
2005-03-21 1:55 ` Simon Richter
2005-03-22 4:19 ` Simon Richter
2005-03-22 4:21 ` Andreas Schwab [this message]
2005-04-04 14:08 ` Richard Earnshaw
2005-04-04 14:10 ` Richard Earnshaw
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=je1xa85vte.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=Simon.Richter@hogyros.de \
--cc=binutils@sourceware.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).