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,15239bed02372eea
X-Google-Attributes: gid103376,public
From: bobduff@world.std.com (Robert A Duff)
Subject: Re: GNAT 3.04a & Environment space
Date: 1996/08/16
Message-ID: <Dw8H7y.22@world.std.com>#1/1
X-Deja-AN: 174671341
references: <4v0q0e$cbq@newsbf02.news.aol.com> <Dw8FF4.6Js@world.std.com>
organization: The World Public Access UNIX, Brookline, MA
newsgroups: comp.lang.ada
Date: 1996-08-16T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <Dw8FF4.6Js@world.std.com>,
I <bobduff@world.std.com> wrote:
>I also had luck with putting "call ...\setpath" in my autoexec.bat file.
>I don't know if this solves the env space problem, ...

Well, it does seem to.  On a different computer, running windows 95, I
put "call c:\gnat304a\setpath" in my autoexec.bat file, and I am now
able to run gnatmake just fine.  I did not fiddle with the "initial
environment" settings (i.e. I disobeyed the README) -- I left it set to
"Auto" (whatever that means).

- Bob