From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,164d3beca632f8b3,start
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1995-01-05 01:25:10 PST
Path: 
 nntp.gmd.de!newsserver.jvnc.net!news.cac.psu.edu!news.pop.psu.edu!psuvax1!uwm.edu!math.ohio-state.edu!caen!msunews!scss3.cl.msu.edu!mrr
From: mrr@scss3.cl.msu.edu (Mark Riordan)
Newsgroups: comp.lang.ada
Subject: GNAT NT 2.0c & LINK32 vs. LINK
Date: 5 Jan 1995 05:17:32 GMT
Organization: Michigan State University
Message-ID: <3efvdc$mp9@msunews.cl.msu.edu>
NNTP-Posting-Host: scss3.cl.msu.edu
X-MSUnetID: mrr
X-Newsreader: TIN [version 1.2 PL1]
Date: 1995-01-05T05:17:32+00:00
List-Id: <comp.lang.ada>

I just spent an interesting half-hour or so with the latest
GNAT for Windows NT (just put up on ftp.cs.yale.edu a day ago).

I learned that GNAT requires the LINK32.EXE from MS Visual C++ 1.10.
I had a heck of a time with the LINK from MSVC 2.0, which is
the current version of Microsoft's NT C compiler.
Fortunately, I also have the older 1.10 release, and eventually
I got GNAT to work after I dug out the older CD-ROM.
The GNAT documentation does warn that LINK32.EXE is required, but
not finding it in my NT 3.5 or MSVC 2.0 distribution, I 
assumed it was an error.

Just a warning that I hope will prevent a few of you from the 
frustration I just went through...
/mrr