public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
* replace mips-*n*bsd in
@ 2003-04-28 20:53 cgd
  2003-04-28 23:16 ` Alan Modra
  0 siblings, 1 reply; 3+ messages in thread
From: cgd @ 2003-04-28 20:53 UTC (permalink / raw)
  To: binutils; +Cc: amodra

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 ;;

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: replace mips-*n*bsd in
  2003-04-28 20:53 replace mips-*n*bsd in cgd
@ 2003-04-28 23:16 ` Alan Modra
       [not found]   ` <mailpost.1051571783.9996@news-sj1-1>
  0 siblings, 1 reply; 3+ messages in thread
From: Alan Modra @ 2003-04-28 23:16 UTC (permalink / raw)
  To: cgd; +Cc: binutils

On Mon, Apr 28, 2003 at 01:53:05PM -0700, cgd@broadcom.com wrote:
> I'd like to see the patch below on the trunk and the branch.  This
> puts the OS names back, for these targets.

That's fine.

> While i'm all for consolidating, is there any reason to take it that
> far?!

To fit them all on one line?  I can't remember why I did it.

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: replace mips-*n*bsd in
       [not found]   ` <mailpost.1051571783.9996@news-sj1-1>
@ 2003-04-28 23:51     ` cgd
  0 siblings, 0 replies; 3+ messages in thread
From: cgd @ 2003-04-28 23:51 UTC (permalink / raw)
  To: amodra; +Cc: binutils

At Mon, 28 Apr 2003 23:16:23 +0000 (UTC), "Alan Modra" wrote:
> On Mon, Apr 28, 2003 at 01:53:05PM -0700, cgd@broadcom.com wrote:
> > I'd like to see the patch below on the trunk and the branch.  This
> > puts the OS names back, for these targets.
> 
> That's fine.

OK, I've taken that as approval-enough.  8-)


> > While i'm all for consolidating, is there any reason to take it that
> > far?!
> 
> To fit them all on one line?  I can't remember why I did it.

Heh.  I know that feeling!


thanks,

chris

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2003-04-28 23:51 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-04-28 20:53 replace mips-*n*bsd in cgd
2003-04-28 23:16 ` Alan Modra
     [not found]   ` <mailpost.1051571783.9996@news-sj1-1>
2003-04-28 23:51     ` cgd

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).