From: Daniel Jacobowitz <drow@false.org>
To: binutils@sources.redhat.com
Subject: Obsolete ARM oabi
Date: Tue, 02 Nov 2004 15:57:00 -0000 [thread overview]
Message-ID: <20041102155739.GA15305@nevyn.them.org> (raw)
The first step is to mark these configurations, which we would like to
remove in 2.16, as obsolete.
Tested with and without --enable-obsolete. OK?
--
Daniel Jacobowitz
2004-11-02 Daniel Jacobowitz <dan@debian.org>
* config.bfd: Mark arm-*-oabi and thumb-*-oabi as obsolete.
Index: config.bfd
===================================================================
RCS file: /big/fsf/rsync/src-cvs/src/bfd/config.bfd,v
retrieving revision 1.174
diff -u -p -r1.174 config.bfd
--- config.bfd 23 Oct 2004 12:23:15 -0000 1.174
+++ config.bfd 2 Nov 2004 15:51:12 -0000
@@ -34,6 +34,8 @@ case $targ in
m68*-*-lynxos* | \
sparc-*-lynxos* | \
vax-*-vms* | \
+ arm-*-oabi | \
+ thumb-*-oabi | \
null)
if test "x$enable_obsolete" != xyes; then
echo "*** Configuration $targ is obsolete." >&2
next reply other threads:[~2004-11-02 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 15:57 Daniel Jacobowitz [this message]
2004-11-02 15:59 ` 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=20041102155739.GA15305@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sources.redhat.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).