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/17
Message-ID: <DwA6LH.H1M@world.std.com>#1/1
X-Deja-AN: 174720067
references: <4v0q0e$cbq@newsbf02.news.aol.com> <Dw8FF4.6Js@world.std.com>
 <Dw8H7y.22@world.std.com> <32152B67.253@telis.org>
organization: The World Public Access UNIX, Brookline, MA
newsgroups: comp.lang.ada
Date: 1996-08-17T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <32152B67.253@telis.org>, Joe DeKeyrel  <dekeyrej@telis.org> wrote:
>I run a similar setup myself (when I'm not running linux). You really
>MUST increase the size of the environment to allow for all the
>environment virables that setpath requires. ...

Well, it may depend on how big those env vars are, which depends on how
long the path name is where you put gnat.  Mine is just c:\gnat304a.
And I suppose it depends on what *other* env vars you have.

I was able to set exactly 1445 bytes of env vars in my autoexec.bat
file.  More than that were ignored without any error message (grr!).
This is plenty for setpath.bat -- as I said, by running setpath.bat from
my autoexec.bat, I am able to run gnatmake just fine WITHOUT fiddling
with the env size.  And I checked that all the vars set by setpath.bat
indeed exist in my MSDOS windows.

On the other hand, if I try to run setpath.bat from an MSDOS window,
it gripes about "Out of environment space".

- Bob