Xref: news-dnh.mv.net comp.os.msdos.djgpp:1604
Path: news-dnh.mv.net!mv!news.sprintlink.net!in1.uu.net!gwu.edu!seas.gwu.edu!ckann
From: ckann AT seas DOT gwu DOT edu (Charles W. Kann)
Newsgroups: comp.os.msdos.djgpp
Subject: Possible stack problem
Date: 16 Aug 1995 19:49:41 GMT
Organization: George Washington University
Lines: 32
Nntp-Posting-Host: 128.164.9.3
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp


I am trying to build gnat2.07 using djgpp.  I am having the same problem as
the person who did the Mac port.  He eventually solved his problem by 
adjusting the stack.  Could something like this cause this type of problem 
on djgpp? If so, what can I set to change it (I found 3 stack variables, 
but all would require that I change the code to make them external.  I 
can do this, but I would rather not).  Can anyone give me some hints?  
Please email me, as I don't always read the list.


> 
> Great news i found the problem with gnat-mac on ppc it was a stack problem
> as i suggested this weekend.  the instructions in machten for configuring
> fragment manager apps (such as gnat1) for a larger than standard stack was
> broken.  Neil Cutcliffe (THANKS NEIL!) at tenon told me how to fix it.  
> When i upped the stack size available to gnat1 i can now compile 
> a-chahan.adb!  i am going to turn loose a build of the gnatk8 and gnatlib 
> now.  
> 
> Chuck, i think the default size for applications build on gcc is a platform
> dependent paramater and is not likely to be solved by gnat-report folks.
> you should look how the pc gcc handles stack size allocations. since you
> are having the same problems i was its at least possible that it will
> solve you problem.

--
chuck kann
ckann AT seas DOT gwu DOT edu

--
chuck kann
ckann AT seas DOT gwu DOT edu