From: cgd@broadcom.com
To: binutils@sources.redhat.com
Cc: amodra@bigpond.net.au
Subject: replace mips-*n*bsd in
Date: Mon, 28 Apr 2003 20:53:00 -0000 [thread overview]
Message-ID: <yov5llxutkcu.fsf@broadcom.com> (raw)
Rev 1.114 of gas/configure.in changed:
! mips-*-elf* | mips-*-rtems* | mips-*-netbsd* | mips-*-openbsd*)
! fmt=elf ;;
to be:
! mips-*-elf* | mips-*-rtems*) fmt=elf ;;
! mips-*-*n*bsd*) fmt=elf ;;
The latter is just too obtuse. Somebody who wants to find the netbsd
configure fragment will have a harder time than they should. (I did!
8-)
I'd like to see the patch below on the trunk and the branch. This
puts the OS names back, for these targets.
Alan, you made the original change:
2002-08-09 Alan Modra <amodra@bigpond.net.au>
* configure.in: bfd_gas=yes for all i386 targets. Formatting.
Remove "bfd_gas=yes" from target table when covered later.
Consolidate some entries.
* configure: Regenerate
While i'm all for consolidating, is there any reason to take it that
far?!
chris
--
[ gas/ChangeLog ]
2003-04-28 Chris Demetriou <cgd@broadcom.com>
* configure.in (mips-*-*n*bsd*): Replace with...
(mips-*-netbsd*, mips-*-openbsd*): These.
* configure: Regenerate.
Index: configure.in
===================================================================
RCS file: /cvs/src/src/gas/configure.in,v
retrieving revision 1.128
diff -u -p -r1.128 configure.in
--- configure.in 1 Apr 2003 15:50:29 -0000 1.128
+++ configure.in 28 Apr 2003 20:50:43 -0000
@@ -373,7 +373,8 @@ changequote([,])dnl
mips-*-sysv4*MP* | mips-*-gnu*) fmt=elf em=tmips ;;
mips-*-sysv*) fmt=ecoff ;;
mips-*-elf* | mips-*-rtems*) fmt=elf ;;
- mips-*-*n*bsd*) fmt=elf ;;
+ mips-*-netbsd*) fmt=elf ;;
+ mips-*-openbsd*) fmt=elf ;;
mips-*-vxworks*) fmt=elf ;;
mmix-*-*) fmt=elf ;;
next reply other threads:[~2003-04-28 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 20:53 cgd [this message]
2003-04-28 23:16 ` Alan Modra
[not found] ` <mailpost.1051571783.9996@news-sj1-1>
2003-04-28 23:51 ` cgd
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=yov5llxutkcu.fsf@broadcom.com \
--to=cgd@broadcom.com \
--cc=amodra@bigpond.net.au \
--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).