Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!decwrl!ogicse!pdxgate!eecs.cs.pdx.edu!deo
From: deo@eecs.cs.pdx.edu (Steven Furber)
Newsgroups: comp.os.minix
Subject: How to install GCC on MacMinix
Message-ID: <627@pdxgate.UUCP>
Date: 10 Nov 90 05:32:40 GMT
Sender: news@pdxgate.UUCP
Reply-To: deo@eecs.cs.pdx.edu (Steven Furber)
Organization: Portland State University, Portland, OR
Lines: 79

Several people have asked for tips on getting GCC to work for MacMinx.
The following should be more than enough information to do so.  I would
like to thank the people that gave me the information needed to get GCC
up and running, and especially Jwahar R. Bammi for porting it to ST Minix.
I have mainly concentrated on Minix itself, and not using ftp.  Let me
know if you have any problems with this and I will update it.  I have
not tested this-- I wrote it from memory.

I ftp'd all of the GCC files from atari.archive.umich.edu.  The directory
is atari/gnustuff/minix.  The files you want are gccbin.tar.Z, gcclib.tar.Z,
and include.tar.Z.  (Note: the extensions of the file names MAY not be the
exact same, but from the above should be close enough to get a match.)

Once you have located these files, MAKE SURE that you are in binary mode.

Once you have all of the files on your local site, uncompress them and then
recompress them with '-b 13' to make SURE that they are 13 bit compressed
instead of 16; I do not know for sure how they are stored, but I do not
like wasting all of my time moving 2+ megs of files.

Next transfer them.  I wanted to transfer them to my MacOS filesystem
instead of Minix because (no offense) Kermit is just too slow.  What I use
is Zterm 0.90, which is about as fast as it gets.  Once all of your files
are downloaded, the real fun begins.  Grab a sixpack, because this will
take some time.

Boot MacMinix.

Time for a decisions-- GCC takes over 1.6mg when it's uncompressed and untar'd.
You're going to want to keep compies of the original files around, too, so
there's around 3mg of space in the end.  Since these files will be going into
a various directories under /usr/local (you create ../local)-- and it MUST be
/usr/local, you need to decide whether you want to create and mount a file-
system or simply jam all of this onto the current filesystem.  I made a 10mg
filesystem and mounted it on /usr/local.  (See 5.7.4 in the documentation for
information on making filesystems.)  Either way, make sure that you have
the following directories:
	/usr/local
	/usr/local/lib
	/usr/local/gcc-include
Find some directory for placing the files you just downloaded; it really
doesn't matter..I have a /u/gnu directory for all of the GNU stuff I grabbed.
For each of the files we'll want to bring them in using 'macread'.  (If you
forgot the filenames, use 'macfile drive:path..' to take a look at what they
are; where path.. is the directory path.)  My files were in slave:Zmodem,
and this is what I typed:
	macread slave:Zmodem:gccbin.tar.Z > gccbin.tar.Z
	macread slave:Zmodem:gcclib.tar.Z > gcclib.tar.Z
	macread slave:Zmodem:include.tar.Z > include.tar.Z
While you could pipe the output from 'macread' into 'uncompress', chances
are that you will run into memory problems.  Besides, you'll want to keep
the compressed files around.

When you've done all of this, 'decompress' them all.  If nothing else is in
the directory, just use:
	decompress *
Next the fun part begins.  You'll want to do the following, only using your
directory instead of /u/gnu:
	cd /usr/local/lib
	tar xvf /u/gnu/gccbin.tar
	tar xvf /u/gnu/gcclib.tar
	cd /usr/local/gcc-include
	tar xvf /u/gnu/include.tar
Now that all of the files are untar'd, it's time to make sure they have
enough memory.  The 'cmem' file may work for others, but it doesn't give
enough space for gcc-cc1.  To make sure we have enough memory, do the
following:
	cd /usr/local/lib
	chmod +x cmem
	chmem =1500000 gcc-cc1      [* see note *]
	mv gcc /usr/bin/.
This will change the memory allocations and move gcc to /usr/bin.  NOTE:
gcc-cc1 takes a lot of memory to run.  I have 4mg of RAM in my machine and
I have 2000000 bytes (2mg) allocated for it.  1.5mg will probably suffice.

You should now be ready to use GCC.  I have not tried rebuilding Minix with
GCC yet, nor do I know if it will work on a non-ST machine.
---
Steven Furber, reliably steven@m2xenix.psg.com