public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Robert Lipe <robertl@dgii.com>
To: gas2@cygnus.com
Cc: jkj@sco.com, rr@sco.com
Subject: bfd patch to flip OpenServer defaults
Date: Mon, 26 Jan 1998 23:05:00 -0000	[thread overview]
Message-ID: <19980127010448.34173@dgii.com> (raw)

I was the one that made this decision two-ish years ago.   It was
the thing to do at the time.   Now I'd like to change it.

OpenServer is a mixed COFF and ELF target. [ If I knew what a pain
two years ago this was going to be, I would have never thought about
supporting it... ] At the time, it looked like COFF was going to stay
strong.  Now, the newer versions of SCO's own tools don't generate COFF
and COFF is quickly becoming the second-class citizen.  This patch
reverses the BFD defaults and will improve our ability to place nicely
with GCC 2.8.0 which emits ELF by default.


Tue Jan 27 01:00:40 1998  Robert Lipe  <robertl@dgii.com>
	* config.bfd (i[3456]86-sco3.2v5*) ELF now the default. 
	(i[3456]860sco3.2v5*coff) an optional build mode.

$ diff -u config.bfd_ config.bfd
--- config.bfd_ Fri Jan 23 03:17:19 1998
+++ config.bfd  Tue Jan 27 00:47:52 1998
@@ -146,8 +146,11 @@
     ;;
 #endif /* defined (HOST_HPPAHPUX) || defined (HOST_HPPABSD) || defined (HOST_HP
PAOSF) */

+  i[3456]86-*-sco3.2v5*coff)
+    targ_defvec=i386coff_vec
+    ;;
   i[3456]86-*-sysv4* | i[3456]86-*-unixware | i[3456]86-*-solaris2* | \
-  i[3456]86-*-elf | i[3456]86-*-sco*elf* | i[3456]86-*-freebsdelf* | \
+  i[3456]86-*-elf | i[3456]86-*-sco3.2v5* | i[3456]86-*-freebsdelf* | \
   i[3456]86-*-dgux*)
     targ_defvec=bfd_elf32_i386_vec
     targ_selvecs=i386coff_vec

-- 
Robert Lipe       http://www.dgii.com/people/robertl       robertl@dgii.com

                 reply	other threads:[~1998-01-26 23:05 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=19980127010448.34173@dgii.com \
    --to=robertl@dgii.com \
    --cc=gas2@cygnus.com \
    --cc=jkj@sco.com \
    --cc=rr@sco.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).