From: elf AT netcom DOT com (Marc Singer)
Message-Id: <199704032131.NAA29993@netcom23.netcom.com>
Subject: Re: Building djgpp on NT Machine (was Nmake for WinNT 3.5 utilities)
To: ckcorcor AT p5 DOT csrd DOT uiuc DOT edu (Casey Corcoran)
Date: Thu, 3 Apr 1997 13:31:12 -0800 (PST)
Cc: djgpp AT delorie DOT com (DJGPP List Alias)
In-Reply-To: <Pine.LNX.3.95.970403094921.15388E-100000@p5.csrd.uiuc.edu> from "Casey Corcoran" at Apr 3, 97 10:00:06 am
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1719      

> No, I'm talking about compiling the djgpp sources on my NT machine.  We've
> scrapped the idea of using MSVC at all.  We're going to do it the
> "traditional" way using editors and RHIDE where we can.  First,
> though, I need to get djgpp to compile on my machine.  I've successfully
> compiled gcc on sunos, linux, and irix boxes in the past . . . but I have
> never had as hard a time as getting djgpp to compile on my NT machine . .
> .  And I think it's because I don't have the right tools (i.e. make
> program).  Basically what I need is a list of tools and versions and a
> step-by-step list of how to build it.  The GNU CC installation
> instructions just aren't specific enough for the DOS/Windows platform.  So
> far, though, I haven't located anyone who has this kind of information :(
> . . .  sigh.

It is not clear to me (even though I have followed this thread) why
you want DJGPP on WinNT.  Recall that DJGPP is explicitly designed to
allow 32 bit programs to run on 16 bit DOS.  It runs on Windows95 and
WinNT because those operating systems emulate the DOS mode.  The
Cygnus project is working to solve the real problem which is to
provide a true port of GNU tools to WindowsNT.  It is a *very*
non-trivial task due to the semantic differences between UNIX and NT. 

WRT compiling DJGPP on NT: I have tried to do this and found that NT
is very reluctant to cooperate.  It appears that the NT support for
DOS is *not* really compatible:

  1) They use the environment variable Path instead of PATH.
  2) Long command line support appears (not robustly evaluated by me)
     to be handicapped or dysfunctional.

I think there was more, but I do not remember all of the problems I
had.

-- Marc Singer