[comp.os.minix] rebuilding libraries

jon@amc.UUCP (Jon Mandrell) (11/03/87)

As a learning experience I decided to rebuild the compile libraries
under minix.  I compiled them, and then archived them, but ran into a
few problems:

1) Some data items were not found in the assembly modules.  I had
   to change the code to insert a '.define' at the start of the files.
2) When looking at the files that are already in the archive, I see that
   the assembly modules are packed assembly code too.  And yet the names
   are the same as the unpacked modules.  I renamed all of the assembly
   modules with a '.asm' extension, and libpack'd them to '.s' which seems
   to work.

Am I missing something here?  After all of this it seems to work, but
I sure went in circles for a while.

-- 
Jon Mandrell, Applied Microsystems Corp., (ihnp4!uw-beaver!tikal!amc!jon)

Jung vs Ze G. jrer tnl?  Jbhyqa'g "Gur N Grnz" gnxr ba n jubyr
qvssrerag zrnavat?

ncoverby@ndsuvax.UUCP (Glen Overby) (11/05/87)

In article <545@amc.UUCP> jon@amc.UUCP (Jon Mandrell) writes:
>1) Some data items were not found in the assembly modules.  I had
>   to change the code to insert a '.define' at the start of the files.

That was an oversight on Dr.  Tannenbaum's part.  I also found out (the
hard way) that the .define must be at the BEGINNING of the file --
nothing, not even comments may proceed it. 

>2) When looking at the files that are already in the archive, I see that
>   the assembly modules are packed assembly code too.  And yet the names
>   are the same as the unpacked modules.  I renamed all of the assembly
>   modules with a '.asm' extension, and libpack'd them to '.s' which seems
>   to work.

There doesn't seem to be any real difference (except in size) whether or
not the files are packed or not. 

I had a lot of problems with ordering the library.  I upgraded my
release 1.1 to 1.2 using the diffs posted here some time back.  The
'run' program supplied with 1.2 didn't do an adequate job with putc(). 
My solution was to compile all the libraries on our VAX and use 'lorder'
and 'tsort' there.  Unfortunately, that hasn't solved all of my
problems.  I am still finding occasional misorderings, one notable case
being a variable, '_M'.  Has anybody else had problems like this?

When doing an assingment for our operating systems course (we're using
Minix this quarter), I found that asctime and ftime(3) are missing, so
ctime(3) doesn't work. It made completing the assignment rather mean.
-- 
Glen Overby
Bitnet: ncoverby@ndsuvax 
UUCP: uunet!ndsuvax!ncoverby