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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,f93aaab45e1d9398 X-Google-Attributes: gid103376,public From: Bob Crispen Subject: Re: gnat compiling error Date: 1996/03/25 Message-ID: <9603251507.AA01907@eight-ball>#1/1 X-Deja-AN: 144162319 sender: Ada programming language comments: Gated by NETNEWS@AUVM.AMERICAN.EDU newsgroups: comp.lang.ada Date: 1996-03-25T00:00:00+00:00 List-Id: nobody@NOWHERE.AMERICAN.EDU asks: >I was wondering if any one can help me. I am trying to get gnat 3.01a for >win95 to compile. [snip] >p.s. the only thing that I did to run the win95 gnat was to run the setup and >then run setpath.bat from a dos prompt and compiled (tried) from the same dos >prompt. Are you sure you didn't get an error message from setpath.bat? On my machine I had to edit the PATH line to put double quotes around the whole string -- if you've got a long filename with embedded spaces, as for example "Program Files", you've got to have the quotes. I'm responding here to an anonymous poster (and, btw, Mr. Nobody, the likelihood of getting help from folks on Usenet when you don't use your name varies between slim and none) because I think that not everyone who uses gnat has my advanced state of Win95/DOS knowledge (which I characterize as being one small but extremely important step above butt ignorant). Putting the double quotes in the PATH line is harmless if there are no embedded spaces and avoids an error when there are. Bob Crispen revbob@eight-ball.hv.boeing.com Speaking for myself, not my company