From: Joel Sherrill <joel@OARcorp.com>
To: gas2@cygnus.com
Subject: patch for i386-go32-rtems in gas-971208
Date: Mon, 22 Dec 1997 08:47:00 -0000 [thread overview]
Message-ID: <Pine.BSF.3.96.971222104422.23375H-100000@vespucci.advicom.net> (raw)
With the patch below my signature, i386-go32-rtems works again in
gas-971208 just as in binutils 2.8.1.
--joel
Mon Mar 31 16:31:04 1997 Joel Sherrill <joel@oarcorp.com>
* bfd/config.bfd (i[3456]86*-go32-rtems*): Fix to be the same
as i[3456]86-go32.
* gas/configure.in (i386*-go32-rtems*): Fix to be the same
as i[3456]86-go32.
diff -r -c gas-971208-orig/bfd/config.bfd gas-971208/bfd/config.bfd
*** gas-971208-orig/bfd/config.bfd Mon Dec 8 03:18:59 1997
--- gas-971208/bfd/config.bfd Sat Dec 20 14:21:49 1997
***************
*** 152,158 ****
targ_defvec=bfd_elf32_i386_vec
targ_selvecs=i386coff_vec
;;
! i[3456]86-*-msdosdjgpp* | i[3456]*-*-go32*)
targ_defvec=go32coff_vec
targ_selvecs="go32stubbedcoff_vec i386aout_vec"
;;
--- 152,158 ----
targ_defvec=bfd_elf32_i386_vec
targ_selvecs=i386coff_vec
;;
! i[3456]86-*-msdosdjgpp* | i[3456]*-*-go32* | i[3456]86-go32-rtems* )
targ_defvec=go32coff_vec
targ_selvecs="go32stubbedcoff_vec i386aout_vec"
;;
diff -r -c gas-971208-orig/gas/configure.in gas-971208/gas/configure.in
*** gas-971208-orig/gas/configure.in Mon Dec 8 03:30:17 1997
--- gas-971208/gas/configure.in Mon Dec 22 10:40:41 1997
***************
*** 167,173 ****
i386-*-coff | i386-*-sysv* | i386-*-sco* | i386-*-isc*)
fmt=coff ;;
i386-*-vsta) fmt=aout ;;
! i386-*-msdosdjgpp* | i386-*-go32*)
fmt=coff em=go32;;
i386-*-rtems*) fmt=coff ;;
i386-*-gnu*) fmt=elf ;;
--- 167,173 ----
i386-*-coff | i386-*-sysv* | i386-*-sco* | i386-*-isc*)
fmt=coff ;;
i386-*-vsta) fmt=aout ;;
! i386-*-msdosdjgpp* | i386-*-go32* | i386-go32-rtems*)
fmt=coff em=go32;;
i386-*-rtems*) fmt=coff ;;
i386-*-gnu*) fmt=elf ;;
reply other threads:[~1997-12-22 8:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.BSF.3.96.971222104422.23375H-100000@vespucci.advicom.net \
--to=joel@oarcorp.com \
--cc=gas2@cygnus.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).