Path: utzoo!utgpu!watserv1!watmath!att!occrsh!uokmax!apple!usc!ucsd!helios.ee.lbl.gov!nosc!crash!pnet01!jca
From: jca@pnet01.cts.com (John C. Archambeau)
Newsgroups: comp.os.minix
Subject: Re: make(1)ing fs, mm, kernel
Message-ID: <2987@crash.cts.com>
Date: 3 Jun 90 20:16:03 GMT
Sender: root@crash.cts.com
Organization: People-Net [pnet01], El Cajon CA
Lines: 59
X-Local-Date: 3 Jun 90 13:16:03 PDT

kjh@pollux.usc.edu (Kenneth J. Hendrickson) writes:
>Stupid question time.  I can't make(1) fs, mm, or the kernel.  I get an
>error message about running out of memory.  I have scads of memory.  I
>have a RAM disk with more than 2 Megs free.  I have 640 k to run
>processes in.  I tried the chmem(1) thing, but I'm not sure exactly
>which program I should be using it on, or exactly how.
>
>Everything else compiled fine, including the library!  I have everything
>else for 1.5.10 built.  I need to build the important parts of the
>kernel now.  I can't figure out the Makefile, to do it by hand.  What
>does:
>
>	file:	Makefile [some file names]
>
>mean?  Makefile is not an executable.  It is also not a shell script.

That's a rule for make on how to make file.  File depends on Makefile and
[some file names].  I could go on for awhile on how make works on your typical
system since make is a fairly powerful utility.  It sure beats doing cc by
hand all the time.

>How do you 'run' the 'Makefile' program?  Please help.  Thanks.

The command to execute a makefile is called make.  When you do a 'make' it
goes through the makefile and executes the necessary commands to make the
program.  I don't know the differences between 1.5.10 and 1.3, but I'd assume
that the semantics would be the same.  Say you only wanted to make the fs
module, well, there's a rule in the makefile which tells the make proggram how
to make fs.  So to make the fs, you do the following from your shell prompt:

make fs

Just be sure you're in the directory where the makefile in question lies.  If
you want to know what make is going to do, but not execute any of the
commands, you can do this:

make -n

Make will print to standard output what it intends to do without doing it. 
See the man/help page for make or in the back of the text for more
information.

As for the memory problem, I'd bump up the memory to the maxmum on all the
compiler passes and make.

Ex.: chmem +64000 /usr/lib/asld

This should get you rolling.  If not, let us know, somebody will answer you.
 
     // JCA

 /*
 **--------------------------------------------------------------------------*
 ** Flames  : /dev/null                     | Small memory model only for
 ** ARPANET : crash!pnet01!jca@nosc.mil     | Unix?  Get the (*bleep*) out
 ** INTERNET: jca@pnet01.cts.com            | of here!
 ** UUCP    : {nosc ucsd hplabs!hd-sdd}!crash!pnet01!jca
 **--------------------------------------------------------------------------*
 */