Date: Thu, 08 Dec 1994 21:10:55 -0500 (CDT)
From: Aaron Ucko <UCKO AT VAX1 DOT ROCKHURST DOT EDU>
Subject: Re: object file format change?
To: nigel AT algor DOT co DOT uk
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
Organization: Rockhurst College; Kansas City, MO

>cross-compiler using --target=i386-go32.  Linux is a red herring:
>there all sorts of different Unix systems (e.g. FreeBSD) with
>different native object code formats, why should we choose to be
>"compatible" with Linux only?
Because Linux is the most popular Intel-based Unix implementation.

>And when Windoze95/Chicago eventually arrives, how much longer will
>vanilla MSDOS survive: Chicago runs 32-bit NT/COFF executables too.
It can, but those executables are going to have a rather hard time
interfacing with the user unless they're built with Micro$oft's
proprietary headers and libraries...besides, many DJGPP users, IMHO,
use Windoze no more than strictly necessary.

>NT-compatible COFF.  It is a golden opportunity that Microsoft picked
>an object code format which is easily supported by the GNU tools.
>
>Products like Toolbuster use GCC to provide a Unix compiler and
>run-time environment for NT/Chicago, but you have to pay for them.  It
>would be great if DJGPP could form the basis of a free alternative.
Again, how would this be possible?  Micro$oft does _not_ want
to give away its SDK for free, and without it you really can't
do a whole lot if you want Windoze to run your executable in its
native mode.

--- Aaron Ucko (ucko AT vax1 DOT rockhurst DOT edu; finger for PGP public key) -=- httyp!
-=*=-Just because you're paranoid doesn't mean they aren't out to get you.-=*=-
Geek code 2.1 [finger hayden AT vax1 DOT mankato DOT msus DOT edu for explanation]: 
 GCS/M/S d(-) H s g+ p? !au a-- w+ v+ C++(+++)>++++ UL++(-)(S+)>++++ P++ 
 L+(++) 3(-) E-(----) !N>++ K- W-(---) M-(--) V(--) po-(--) Y+(++) t(+) !5 j R 
 G tv--(-) b+++ !D(--) B--(---) e>++++(*) u++(@) h!() f(+) r-(--)>+++ n+(-) y?