Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ihnp4!ptsfa!lll-lcc!seismo!nbires!hao!noao!mcdsun!fnf
From: fnf@mcdsun.UUCP
Newsgroups: comp.os.minix
Subject: Re: portablity bug in mkfs.
Message-ID: <296@mcdsun.UUCP>
Date: Sat, 11-Apr-87 17:04:11 EST
Article-I.D.: mcdsun.296
Posted: Sat Apr 11 17:04:11 1987
Date-Received: Wed, 15-Apr-87 00:29:18 EST
References: <956@ark.cs.vu.nl> <1660@ttrdc.UUCP>
Reply-To: fnf@mcdsun.UUCP (Fred Fish)
Organization: Motorola Microcomputer Division
Lines: 33
Keywords: mkfs

In article <1660@ttrdc.UUCP> levy@ttrdc.UUCP (Daniel R. Levy) writes:
>Can someone please explain to me why one would try to compile MINIX source on
>a VAX.  Just curious.

How about:

	(1)	Find compiler dependencies (questionable C code that
		is acceptable to one compiler and not another).

	(2)	Find machine dependencies (byte order, primitive object
		sizes, structure alignment and padding, etc).

	(3)	Find environment dependencies (missing include files,
		missing or nonstandard library functions, etc)

	(4)	Run lint on the sources.

	(5)	Run cxref on the sources.

	(6)	Run useful minix utilities on unix (are there any
		that unix doesn't have?)

	.
	.
	.

-Fred


-- 
= Drug tests; just say *NO*!  (Moto just announced new drug testing program)  =
= Fred Fish  Motorola Computer Division, 3013 S 52nd St, Tempe, Az 85282  USA =
= seismo!noao!mcdsun!fnf    (602) 438-5976                                    =