paone@topaz.rutgers.edu (Phil Paone) (09/30/88)
Help... I downloaded the gcc arc files about a week ago. I think I followed the directions exactly, but I keep getting two bombs. I am running it from gulam as suggested and I have 1 meg of memory. Another thing is the stack size. Someone posted a change of 500000 to 300000. Is that a decimal value? The hex is 7A120, but changing that didn't help either. Any suggestions? !rutgers.edu!topaz!paone -- Phil Paone paone@topaz.rutgers.edu ihnp4!moss!oac!ppaone "Admiral...There be whales here"
franco@iuvax.cs.indiana.edu (10/01/88)
The 7A120 should be changed to 20000 (about 130k) and gulam cannot be used because it is too big. However, Bammi wiped up a "minimal shell" that takes only 20-30k which does fine with the compiler. I can post it if there is demand.
tar@naucse.UUCP (Tim Roeder) (03/14/90)
I am currently attempting to build the GEM programming envelope library from Compute!'s ST Applications Guide (Programming in C). Since I am using GNU C v. 1.37 instead of the Alcyon C as in the book, I have run into a small problem. In one of the functions named 'doarrows.c', there is the line: #include <document.h> My distribution of GNU C does not have the said header file, and I cannot find an equivalent within ANY of the header files. When attempting to compile the function, I get the warning that: NLINES (not defined) NCHARS (not defined) I presume that these are defined in <document.h>. Could some kind soul who has the Developer's Kit tell me whether or not there is a <document.h> include file? And if so, what values are NLINES and NCHARS supposed to be defined as having? Thank you in advance for any help. -- Timothy A. Roeder - Northern Arizona University/Univeristy of Arizona UUCP: ...!arizona!naucse!tar Internet: arizona.edu!naucse!tar -- troeder@mis.arizona.edu Bitnet: roedert@arizvm1.BITNET
tar@naucse.UUCP (Tim Roeder) (03/14/90)
In regards to my post about help finding a particular header file, please disregard. I discovered the necessary header file <document.h> buried deep within the book that I am using at the moment. Things would be MUCH easier if the authors had documented (preferably in an index) extacly which functions/headers files/etc., can be found in the text and which are found only in the Developers Kit. Sorry for any wasted bandwidth. Regards, -- Timothy A. Roeder - Northern Arizona University/Univeristy of Arizona UUCP: ...!arizona!naucse!tar Internet: arizona.edu!naucse!tar -- troeder@mis.arizona.edu Bitnet: roedert@arizvm1.BITNET