nall@sun8.scri.fsu.edu (John Nall) (10/11/90)
The time has finally come (the walrus said...) to proceed
with the upgrade to Minix-386. I've started, and have run
into a minor problem -- perhaps someone would be so kind as
to send me a brief note as to the problem.
I have done the following:
(1) Pulled everything from the "oz" subdirectory
of plains.nodak.edu (yes, I know that I will
not need it all for Minix-386, but most of it
I wanted in any case).
(2) Did the necessary unpacking etc.
(3) Made a directory structure that follows the
outline of the "runtime.crc" file which is
in the mx386_1.1 subdirectory.
(4) Begun moving files to flesh out the directory
structure, and checking crc's to be sure they
match.
This is where the problem is. Bruce seems to have two sets
of include nad library files. For example:
/usr/include/dist/lib.h
and
/usr/include/lib.h
The /usr/include/dist/lib.h appears to be the distributed
version (presumably that is what the dist stands for), and the
crc checks ok.
However, I cannot find in any of the oz files that I got another
copy of lib.h. There are quite a few that are in this same
category. They are:
(under /usr/include/)
fcntl.h, lib.h, limits.h, math.h, stdlib.h, and unistd.h
(under /usr/src/lib/ansi/)
assert.c, ctime.c, difftime.c, strtol.c, strtoul.c
(under /usr/src/lib/other/)
lock.c, nlist.c
(under /usr/src/lib/posix/)
execlp.c, getcwd.c
Also, so long as I am asking, I am going on the presumption that
I should use bcc32 from the start (in order to build the 386 kernel),
and that there is no need to use bcc16 at all. Is that correct? Or
is there some sort of bootstrapping necessary which utilizes bcc16?
Thanks for any info. Please e-mail me directly. I'm going to try and
keep a good set of notes as I go, and will try and make up a tutorial
after I finish for net distribution (following Glen Overby's example).
--
John W. Nall | Supercomputation Computations Research Institute
nall@sun8.scri.fsu.edu | Florida State University, Tallahassee, FL 32306
"Real programmers can write assembly code in any language." - Larry Wallnall@sun8.scri.fsu.edu (John Nall) (10/12/90)
In article <1091@sun13.scri.fsu.edu> nall@sun8.scri.fsu.edu I wrote: >The time has finally come (the walrus said...) to proceed >with the upgrade to Minix-386. I've started, and have run > >This is where the problem is. Bruce seems to have two sets >of include and library files. For example: > > /usr/include/dist/lib.h > and > /usr/include/lib.h > Stupid, stupid, stupid! I just didn't look hard enough. They are there (in the bcclib stuff). :-< However, although I have all the library files cleared up, and crc's check on almost everything, I STILL have some bad crc's on some files in /usr/src/tools (as indicated in Bruce's list). To wit: /usr/src/tools bootblok.s, build.c and menu1.s Are there some .cdif files for these? Also, the crc on /usr/src/mm/makefile.cpp is wrong. Bruce shows 63284 2009 /usr/src/mm/makefile.cpp and I show 07128 1942 /usr/src/mm/makefile.cpp Since this file came directly from the archives, I'm not sure why there is a problem. Anyone know? Thanks for any any and all suggestions. -- John W. Nall | Supercomputation Computations Research Institute nall@sun8.scri.fsu.edu | Florida State University, Tallahassee, FL 32306 "Real programmers can write assembly code in any language." - Larry Wall