Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!amdcad!sun!pitstop!sundc!seismo!uunet!mcvax!hp4nl!philmds!nlgvax!johan
From: johan@nlgvax.UUCP (Johan Stevenson)
Newsgroups: comp.os.minix
Subject: Re: recompiling MINIX on ST
Keywords: general setup
Message-ID: <157@nlgvax.UUCP>
Date: 17 Nov 88 19:58:19 GMT
References: <561@mks.UUCP>
Reply-To: johan@nlgvax.UUCP (Johan Stevenson)
Organization: Philips Research Geldrop
Lines: 39

In article <561@mks.UUCP> wheels@mks.UUCP (Gerry Wheeler) writes:
	>
	>I have just recently recompiled MINIX-ST, and thought I would mention
	>some of the steps I had to use. 
	>
	>The first thing I came across was a lack of stack space in cem when
	>compiling files in the kernel.  I have now increased cem's stack+heap
	>space to 70000. 
You are advised to do so in the user manual (Section 2.5, page 9).
	>
	>Of course, that made cem too large for my memory, because I had set up a
	>512K ram disk.  So, I trimmed it down to 200K. 
Even with 512K ram disk and 70000 stack space for cem you can compile.
You can NOT just say 'make'. You have to use the 'make -n' trick:

	$ make -n >x
	$ . x

Unfortunately this is NOT documented in the user manual.
However, the user manual (Section 3.4, page 25) describes the 'cc -vn'
trick that works in even more restricted situations, but is a little
more cumbersome:

	$ >job
	$ make CC='cc -vn 2>>job'
	$ . job

Hope this clarification helps.

	>
	>Now I have found that fsck won't compile because of lack of space in
	>/tmp.  You can't win, eh? I suspect there is a balance between stack
	>space in cem and ram disk size that will work.  (Or maybe I'll use the
	>-T option to put the temp files elsewhere when compiling fsck.)

This is indeed the right solution once you have trimmed down the
ROOT file system (see Section 3.4, page 23).
--
Johan W. Stevenson	johan@pcg.philips.nl		Philips Research