Path: utzoo!utgpu!watmath!uunet!portal!cup.portal.com!thad From: thad@cup.portal.com (Thad P Floryan) Newsgroups: unix-pc.general Subject: Re: Fed up with Gnu CC Message-ID: <12042@cup.portal.com> Date: 3 Dec 88 03:11:50 GMT References: <450@manta.pha.pa.us> <12015@cup.portal.com> Distribution: unix-pc Organization: The Portal System (TM) Lines: 32 Though most the GNU software compiles (and executes!) fine on the UNIXpc, attempts to build GNU gcc (version 1.31) run up against what appears to be an insurmountable obstacle: lack of table space in the UNIXpc cc compiler. Specifically: following ALL the GNU instructions, running the config.gcc script and specifying ``3b1'', etc etc etc, THEN invoking "$ make", a humongous number of "too much defining" error messages result (from either building the gnulib or gcc). I've checked all the supplied docs for cc and cpp (for the UNIXpc) and there is no mention of any switch or option that may rectify this problem. The AT&T docs add insult to injury by suggesting: "The diagnostics produced by C itself are intended to be self-explanatory." (The preceeding quote from both the User's Manual and the Programmer's Guide. Sheesh.) Further perusal of the docs turns up NO descriptions of error messages. Has anyone encountered this problem ("too much defining") and solved it? If it *IS* a situation of too many "#define ...", any suggestions for a possible workaround? How have those who've build gcc before (on the UNIXpc) side-stepped this problem? The GNU docs clearly state to *NOT* use gcc itself to build the gnulib and the first stage of compiling gcc, thus precluding use of, say, gcc-1.26 or the recently posted gcc-1.30. Thad Floryan [ thad@cup.portal.com (OR) ..!sun!portal!cup.portal.com!thad ]