agw@cs.columbia.edu (Art Werschulz) (02/28/91)
Hi all.
While compiling the file input.c from the X11R4 version of xtrek, the
C compiler complained that there was insufficient space to do the
compilation, and gave up. (Sorry I don't have the exact msg with me,
but that machine is not on the Net.)
Anybody know how to get around this?
--
Art Werschulz
InterNet: agw@cs.columbia.edu
ATTnet: Columbia University (212) 854-8642 854-2736
Fordham University (212) 841-5323 841-5396frank@leopard.austin.ibm.com (03/02/91)
In article <AGW.91Feb28095317@cs.cs.columbia.edu>, agw@cs.columbia.edu (Art Werschulz) writes: > While compiling the file input.c from the X11R4 version of xtrek, the > C compiler complained that there was insufficient space to do the > compilation, and gave up. I think it means that you don't have enough page space. - Frank Feuerbacher Disclaimer: I don't speak for my employer and they don't speak for me.
prk@planet.bt.co.uk (Peter Knight) (03/04/91)
agw@cs.columbia.edu (Art Werschulz) writes: >Hi all. >While compiling the file input.c from the X11R4 version of xtrek, the >C compiler complained that there was insufficient space to do the >compilation, and gave up. (Sorry I don't have the exact msg with me, >but that machine is not on the Net.) >Anybody know how to get around this? You don't say what version of the system you are running, but some of my colleagues have been building some code originally written for Suns on an RS/6000, and they have had trouble with the linker eating up all the space. Apparently, it doesn't free memory... The work-around used there was to increase the paging space on the hard disk. Hope this helps. Peter Knight BT Research #include <std.disclaimer>
bengsig@dk.oracle.com (Bjorn Engsig) (03/04/91)
Article <AGW.91Feb28095317@cs.cs.columbia.edu> by agw@cs.columbia.edu says: |While compiling the file input.c from the X11R4 version of xtrek, the |C compiler complained that there was insufficient space to do the Increase paging space or ulimit -d, ulimit -m or ulimis -s. -- Bjorn Engsig, ORACLE Corporation, E-mail: bengsig@oracle.com, bengsig@oracle.nl
bengsig@dk.oracle.com (Bjorn Engsig) (03/06/91)
Article <prk.668077483@pegasus> by prk@planet.bt.co.uk (Peter Knight) says: |, and they have had trouble with the linker eating up all |the space. Apparently, it doesn't free memory... Didn't somebody try to create a FAQ list for this newsgroup. I guess I should put the text "The AIX 3.1 linker is very different from what you are used to and can use quite large paging space" in my signature. (Mr. Knight, I know you know about this, so please don't feel accused). Somebody volunteers as a FAQ maintainer? -- Bjorn Engsig, ORACLE Corporation, E-mail: bengsig@oracle.com, bengsig@oracle.nl
jsalter@ibmpa.awdpa.ibm.com (03/07/91)
In article <1279@dkunix9.dk.oracle.com> bengsig@dk.oracle.com (Bjorn Engsig) writes: >Somebody volunteers as a FAQ maintainer? Yes, someone out of Stanford was originally going to do this, but he's been busy. At the pre-SHARE RISC System/6000 Free-for-All he mentioned it's still in the works. >Bjorn Engsig, ORACLE Corporation, E-mail: bengsig@oracle.com, bengsig@oracle.nl jim/jsalter IBM PSP, Palo Alto T465/(415)855-4427 VNET: JSALTER at AUSVMQ Internet: jsalter@slo.awdpa.ibm.com UUCP: ..!uunet!ibmsupt!jsalter PS/2 it, or DIE! :-) The ramblings above have nothing to do with Big Blue.