🚀 go-pugleaf

In article <3159@ibmpa.UUCP> webb@bass.tcspa.ibm.com (Bill Webb) writes:
  >> Greetings...I am attempting to install gnu-emacs on an IBM PC RT
  >> (running AIX 2.2) with 4 MBytes of memory.  The compilation crashes at
  >> Fatal error in ccom1: Memory fault

  >I suggest that you check to see that you have enough swap space. Since you
  >don't have very much memory (e.g. 4megs) and I suspect that GNU-emacs
  >has some pretty big files, its possible that you don't have enough swap
  >space to compile it. Because AIX doesn't preallocate swap space this is
  >usually evidenced by a Memory fault at run time when the system has to 
  >page out part of your process (the compiler) and there isn't enough 
  >swap space (BSD at least tests before it gives you the memory so that 
  >once processes are given memory the system doesn't usually have to send
  >a nasty signal to the process later on). Another possiblity if you can't
  >easily add swap space is to get rid of all expendable processes to
  >increase the available swap space. In particular, if you're running X windows,
  >shut it down while you do the compile. Also you might be able to cut the
  >compiler memory requirements by dropping out -O (if you're using that).

The above does not jive with my experience.  I've never gotten this
sort of scenario when I've run low on paging space.  What I've seen is
that when you get low on paging space you get a "syncmode entered"
message, with the warning "kill processes now" and then, before I can
manually kill any processes, the system picks the most important
process I'm running, such as the X server or GNUemacs and kills it,
along with several others. :-) But I've never heard of getting a
memory fault from being low on page space.

My suggestion is to upgrade to 2.2.1 and get the latest version of
emacs from prep.  If you can't compile a particular file with -O,
compile it manually without -O and then finish the compilation with
-O.

-- 
Nick Simicich --- uunet!bywater!scifi!njs --- njs@ibm.com (Internet)