Path: utzoo!utgpu!water!watmath!clyde!att!ucbvax!pasteur!helios.ee.lbl.gov!nosc!hall
From: hall@nosc.NOSC.MIL (Robert R. Hall)
Newsgroups: comp.os.minix
Subject: some upgrade to v1.3 problems
Message-ID: <742@nosc.NOSC.MIL>
Date: 20 Jun 88 22:05:13 GMT
Organization: Naval Ocean Systems Center, San Diego
Lines: 58


All of Minix v1.3 library functions compiled without error messages
except for malloc.c which gave me the three warning messages:
  "malloc.c", line 49: (warning) overflow in unsigned constant expression
  "malloc.c", line 68: (warning) overflow in unsigned constant expression
  "malloc.c", line 113: (warning) overflow in unsigned constant expression
To eliminate these error message I patched it with the following diff:

-----------------------------    malloc.dif ----------------------------
14c14
< #define	ptrint		int
---
> #define	ptrint		unsigned
22c22
< #define Align(x,a)	(((x) + (a - 1)) & ~(a - 1))
---
> #define Align(x,a)	(((x) + (a - 1)) & ~((ptrint)(a - 1)))
_______________________________________________________________________

The question is: is this casting necessary or should I ignore the warning
messages, in either case the object code produced by the version 1.1 cem
compiler is different. (I have not seen version 1.2 distributed to the net).
I tried putting this patch using the Mined editor version 1.3 and
discovered that numeric + (search forward), numeric - (search bachward),
numeric 5 (display file status), PgUp, PgDn commands did not function.

So I went back to using the mined version 1.2 editor , where these
particular functions work just fine.

Next I tried to build a libc.a library archive file, following the
example show in Provisional V1.3 doc/man-pages of AST readnews 
messag-ID <709@ast.cs.vu.nl> a READ_ME file for the tsort command
which is shown as:
   ar cr libc.a `lorder *.s` | tsort
and conclude that there is a typo here and the second backward quote
mark belong after tsort and the command example should be:
  ar cr libc.a `lorder *.s | tsort`

This modifed command does work on a small number of the elements but
when applied to commplete library, I got the error message:
  lorder: argument list too long
I find this version 1.3 shell message to be a more accurate discription
of the trouble than version 1.2 message of:
  lorder: can't execute

To build libc.a, I resorted to Glen Overby shell script in his 
message-ID <981@ndsuvax.UUCP>
Next I tried to check for missing library element in the new file
against what I had in the old file /usr/lib/libc.a by using the sort 
command as:
  ar t libc.a | sort -o new
  ar t /usr/lib/libc.a | sort -o org

Version 1.2 of sort only pass on 1/4 of the element names whereas
version 1.3 does the job correctly and is an improvement.

				       Robert R. Hall
				       hall@nosc.mil