Xref: utzoo comp.lang.c++:1617 comp.unix.aux:365 comp.sys.mac.programmer:2450
Path: utzoo!attcan!uunet!lll-winken!lll-tis!mordor!joyce!ames!mailrus!tut.cis.ohio-state.edu!rutgers!apple!mgchow
From: mgchow@Apple.COM (Mike Chow)
Newsgroups: comp.lang.c++,comp.unix.aux,comp.sys.mac.programmer
Subject: Re: C++, A/UX, and Mac OS
Keywords: C++, A/UX, Macintosh
Message-ID: <17272@apple.Apple.COM>
Date: 17 Sep 88 00:37:36 GMT
References: <7114@well.UUCP> <22404@tis.llnl.gov>
Reply-To: mgchow@apple.com.UUCP (Mike Chow)
Organization: Apple Computer Inc, Cupertino, CA
Lines: 19

In article <22404@tis.llnl.gov> tjt@tis.llnl.gov (Tim Tessin) writes:
>In article <7114@well.UUCP> richer@well.UUCP (Mark H. Richer) writes:
...
>I had problems running the C compiler on my machine which is still at
>2mb memory.  This may soon be fixed when my second-source memory 
...

There is also a "large" version of the C compiler for A/UX; it has
much larger symbol tables then standard one.   You can invoke the
large C compiler by using the "-B /usr/lib/big/" option to CC.
It's fairly robust; programs such as Electric, Magic, X11, and
INGRES are all fairly large and have successfully been compiled
with the large C compiler (including a 160 line C macro).

You'll know when to use the large C compiler if the standard A/UX
C compiler dies on a Symbol Table Overflow error.

			Mike Chow
			Apple Computer, Inc.
			mgchow@apple.com