public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: artk@congruent.com (Arthur Kreitman)
To: raeburn@cygnus.com
Cc: gas2@cygnus.com, bfd@cygnus.com, erich@uruk.org
Subject: traditional Intel & Microsoft formats...
Date: Wed, 09 Nov 1994 10:49:00 -0000	[thread overview]
Message-ID: <9411091827.AA08130@Congruent.COM> (raw)
In-Reply-To: <9411091757.AA00676@cujo.cygnus.com>

>   How much would supporting those Microsoft formats buy us over what DJ
>   Delorie has already done with DJGPP and GO32?  (Please excuse my
>   cluelessness, I've never done development on DOS or Windows and know next
>   to nothing about their file formats &c.)

  This would be for native support.  Remember, what go32 does is provide
a 32 bit environment.

>   Hm.  I could believe it might be significantly different from the formats
>   we use on other systems, but man-years of work?  Is it *that* different?
  Its different enough to require two or three people working for six or
nine months.  That's just the binutils side.  That doesn't include MS's
special debugging formats, or the gcc changes needed to really fit in
to MS's world, or doing gdb.

>   The primary goal would be to produce working executables.  Using object
>   and library formats compatible with the native tools would be a plus, but
>   not absolutely necessary, especially if the vendor is anal about releasing
>   information.

  You need to link against microsoft libraries to be able to create an
executable that runs.

>   And given that this vendor is Microsoft, I think we should be especially
>   paranoid about not violating license terms &c, when trying to do any of
>   that reverse engineering...  We don't want to make Cygnus or the FSF an
>   easy lawsuit target.

 Reverse engineering isn't a problem.  Even Microsoft know's that its
not enforcable.  However, it is a ton of work.  I've been trying to
get unencumbered specs (not marked Microsoft Confidential).


>   I agree it's a huge market.  But I'm always skeptical about any numbers
  Prime didn't believe the impact of workstations.  



  parent reply	other threads:[~1994-11-09 10:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1994-11-09  8:05 Erich Stefan Boleyn
1994-11-09  8:59 ` Arthur Kreitman
1994-11-09  9:41   ` Erich Stefan Boleyn
1994-11-09  9:56   ` DJ Delorie
1994-11-09  9:57   ` Ken Raeburn
1994-11-09 10:33     ` DJ Delorie
1994-11-09 11:56       ` Erich Stefan Boleyn
1994-11-09 10:49     ` Arthur Kreitman [this message]
1994-11-09 12:02       ` Erich Stefan Boleyn
1994-11-10  8:22     ` Richard Stallman
1994-11-10  8:11   ` Richard Stallman
1994-11-10  9:35     ` Erich Stefan Boleyn
1994-11-10 22:53 ` John Gilmore
1994-11-10 23:25   ` John Gilmore
1994-11-11  5:34   ` Arthur Kreitman
1994-11-11  8:31     ` Ian Lance Taylor
1994-11-11 10:21   ` Erich Stefan Boleyn

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=9411091827.AA08130@Congruent.COM \
    --to=artk@congruent.com \
    --cc=bfd@cygnus.com \
    --cc=erich@uruk.org \
    --cc=gas2@cygnus.com \
    --cc=raeburn@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).