Article View: gnu.gcc.help
Article #470Re: Problems compiling on i386 Interactive Unix
From: Mark Jeghers -- UNIX/X/Motif Con...
Date: Sun, 11 Oct 1992 06:35
Date: Sun, 11 Oct 1992 06:35
33 lines
1293 bytes
1293 bytes
johnm@cimage.com (John Marshall) writes: >I'm trying to compile gcc version 2.2.2 on a 386 running Interactive Unix. > cc -D_POSIX_SOURCE -g -o cc1 c-parse.o c-lang.o c-lex.o c-decl.o c- . . . etc etc etc . . . >ck.o ` case "cc" in "cc") echo ;; esac ` -lPW -lcposix >ld fatal: fail to write symbol name reg_class in string table for file cc1 >*** Error code 13 >johnm@cimage.com This may sound crazy, but log in as root and set ulimit top some really big value, e.g. ulimit 999999999 At times, I have had compiles fail in gcc and X11R4/5 because the unstripped and debug-padded object code added up more memory than my process was allowed to have. Upping the ulimit parameter fixed the problem quickly. Just a hunch, but who knows? Give it a try. Mark Jeghers UNIX/X/Motif Contractor 408/281-4823 [voicemail]
Technical Details
Message-ID:
<1992Oct11.063542.491@shawn.uucp>Path:
arc1-ca.pugleaf.net!sparky!uunet!decwrl!netcomsv!dlb!shawn!rootReferences:
<1992Oct10.193706.13038@cimage.com>Show Full Headers
Complete Article Headers
Newsgroups: gnu.gcc.help Path: arc1-ca.pugleaf.net!sparky!uunet!decwrl!netcomsv!dlb!shawn!root From: root@shawn.uucp (Mark Jeghers -- UNIX/X/Motif Contractor) Subject: Re: Problems compiling on i386 Interactive Unix Message-ID: <1992Oct11.063542.491@shawn.uucp> Organization: Mark Jeghers -- UNIX/X/Motif Contractor References: <1992Oct10.193706.13038@cimage.com> Distribution: usa Date: Sun, 11 Oct 92 06:35:42 GMT Lines: 34