Path: utzoo!attcan!uunet!husc6!bloom-beacon!gatech!udel!mmdf
From: jnall%FSU.BITNET@CORNELLC.CIT.CORNELL.EDU (John Nall 904-644-5241)
Newsgroups: comp.os.minix
Subject: D1.2-1.3 -- Act II
Message-ID: <5718@louie.udel.EDU>
Date: 28 Nov 88 22:17:49 GMT
Sender: mmdf@udel.EDU
Lines: 38

From the several people who answered my query regarding the D1.2-1.3.tar.Z
file, there were several who said that they had successfully upgraded to
Minix 1.3.  Unfortunately, I don't remember their names (or I would just
e-mail directly, rather than broadcasting to the net).  The following is
a follow-up question:

I've successfully moved the file, and gotten the various parts onto my
AT under Minix.  Now comes the part of compiling the source to make the
new 1.3 version, and I've hit a couple of snags that I can't solve.  I
suspect they're related:

   (1)  When compiling the new minix/commands subdirectory (that is,
doing a make on all of it) I have several unsatisfied externals.  They
are _clean (in animals.c), _fdopen and _exit (in at), and a few more.
I previously did a "run" on minix/lib and moved the resulting lib.ca
to /usr/lib.  (I meant "resulting libc.a...).  But I didn't reorder the
library beyond what run does.  Does that have to be done?

  (2)  Many, many of the minix/commands are getting an error which
says "no space on root device (RAM disk) and the make aborts.  This
includes tsort.c, which is why I didn't run it on libc.a.  How does one
get around this?

  (3)  minix/mm compiles ok.  minix/fs gets an unsatisfied external
(something named _sys_kil)??  minix/kernel gets unsatisfied externals
of _port_in and _port_out.

SO...any suggestions on the unsatisfied externals and no room on RAM disk?
I spent fifteen years as a systems programmer (on Control Data systems)
and don't mind the learning experience, but it takes a while to get
all the details down.

Thanks

John Nall
Department of Computer Science
Florida State University
(jnall@fsu)