Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!claris!apple!voder!pyramid!prls!mips!sultra!dtynan From: dtynan@sultra.UUCP (Der Tynan) Newsgroups: comp.os.minix Subject: Re: D1.2-1.3 -- Act II Summary: Ah, is this Deja Vu, or what? Message-ID: <2688@sultra.UUCP> Date: 30 Nov 88 04:05:32 GMT References: <5718@louie.udel.EDU> Organization: Tynan Computers, Sunnyvale, CA Lines: 46 In article <5718@louie.udel.EDU>, jnall%FSU.BITNET@CORNELLC.CIT.CORNELL.EDU (John Nall 904-644-5241) writes: > > 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 libc.a > to /usr/lib. But I didn't reorder the > library beyond what run does. Does that have to be done? In a word. Yes! Nothing against Art Zemon's nice piece of code, but unfortunately, it is just a stopgap until you can use lorder and tsort. Of course, it's catch-22 time, because if you don't have a good library, you can't make lorder. Either hand-generate the library using ASTs posted 'order', or use my previous posting, to get 'lorder' to work. > (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? Either do what I did (remove the RAMDISK), or clean out everything but the nonessential commands from /bin, /lib, /etc and all the other places. Of course, don't forget to put them back afterwards :-) As a quick check, run df /dev/ram to see just how bad it is. Then, go from there. > (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. > > John Nall The first problem is most likely due to your bad library. The second, is because AST *removed* both those functions from the 1.3c stuff. The cdiff files actually pulled out the functions. Since then, Andy has posted a file called portio.s which has the appropriate routines. Other than that, go back to your 1.2 disks, and pull them out of klib88.s (I think that's where they are). Of course, if you use the peephole optimizer posted some time ago, it replaces all calls to _port_in and _port_out, with inline code, which is a nifty idea. Sometime, when I get a chance (Hah!), I'd like to implement that optimizer... - Der -- dtynan@zorba.Tynan.COM (Dermot Tynan @ Tynan Computers) {apple,mips,pyramid,uunet}!Tynan.COM!dtynan --- If the Law is for the People, then why do we need Lawyers? ---