X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Date: Sat, 19 May 2012 16:46:37 +0300
From: Eli Zaretskii <eliz AT gnu DOT org>
Subject: Re: incompatible
In-reply-to: <jp839g$unq$1@speranza.aioe.org>
X-012-Sender: halo1 AT inter DOT net DOT il
To: djgpp AT delorie DOT com
Message-id: <83fwawz3k2.fsf@gnu.org>
References: <442a0 DOT 580acc3b DOT 3ce7635b AT aol DOT com> <83txzdstc1 DOT fsf AT gnu DOT org> <8c35d644-ede1-4b87-8c60-ebf6a0db0513 AT hq4g2000vbb DOT googlegroups DOT com> <jp6uks$g27$1 AT speranza DOT aioe DOT org> <f2041f3a-3eb3-4fbe-afc1-c4245314b211 AT r3g2000yqh DOT googlegroups DOT com> <jp839g$unq$1 AT speranza DOT aioe DOT org>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: "Rod Pemberton" <do_not_have AT notemailntt DOT cmm>
> Date: Sat, 19 May 2012 08:22:51 -0400
> 
> "Rugxulo" <rugxulo AT gmail DOT com> wrote in message
> news:f2041f3a-3eb3-4fbe-afc1-c4245314b211 AT r3g2000yqh DOT googlegroups DOT com...
> > On May 18, 8:57 pm, "Rod Pemberton" <do_not_h DOT  DOT  DOT  AT notemailntt DOT cmm>
> > wrote:
> ...
> 
> > > DJGPP produces an 32-bit executable in COFF and then stubs it with a
> > > 16-bit stub. So, the 32-bit executable should be able to run in whatever
> > > "console" window is still available in Windows with a working loader
> > > (COFF) or the correct executable format (PE ... ?).
> >
> > No. The BIOS and DOS APIs, not to mention DPMI, are required. I know
> > you already know this. But Win64 lacks all of those.  [...]
> 
> I was glossing over it ...  DJGPP needs a purpose.
> 
> I was noting that DJGPP could move on from DOS to Windows "console"-only
> applications.  It would give the DJGPP project some purpose.  The Windows
> "console" still appears to be a useful platform for CLI programs on Windows.
> 
> "Console" applications aren't DOS, but that's where many DJGPP users are
> currently using DJGPP.  I think the developer's here know that.  It would
> require a rewrite of the custom DOS C library DJGPP uses, which could
> possibly be huge or not.  Or, it could require GLIBC etc to be
> ported

FYI: glibc is a much larger library than the DJGPP library.  And large
parts of it cannot be easily ported to native Windows, because they
are too Posix-centric.  So porting it to Windows is a much larger job
than porting the DJGPP library.

Btw, an old version of glibc was ported to Windows, you can find it on
the net.  But that port left quite a few functions unimplemented.

> I'd assume that Cygwin uses a GLIBC port

It doesn't.  It uses newlib, a different library.