Path: utzoo!attcan!uunet!cs.utexas.edu!wuarchive!julius.cs.uiuc.edu!ux1.cso.uiuc.edu!uxh.cso.uiuc.edu!archetyp
From: archetyp@uxh.cso.uiuc.edu (Joseph R Pickert)
Newsgroups: comp.os.minix
Subject: Re: GCC for MacMinix
Message-ID: <1990Nov5.150310.7875@ux1.cso.uiuc.edu>
Date: 5 Nov 90 15:03:10 GMT
References: <539@pdxgate.UUCP>
Sender: news@ux1.cso.uiuc.edu (News)
Organization: University of Illinois at Urbana
Lines: 28

deo@eecs.cs.pdx.edu (Steven Furber) writes:

>I got a hold of the ST-Minix binaries for GCC, since the 68k Minixes are
>said to be binary compatible.  When I finally got everything downloaded,
>untar'd, and ready to run-- I was a bit depressed with the outcome.

>It does not appear that GCC compiled for ST-Minix will work for MacMinix, as I
>was told it was.

>I have a copy of the diffs needed to get Minix to compiled for the ST, but I
>don't have a copy of gcc.1.36*, all I can find is gcc.1.37*.

>If someone has had any luck, please let me know.

MACMINIX and ST-MINIX are binary compatable (in fact, ST-MINIX elle and
MACMINIX elle are the same binary), so it is PROBABLY something else.
This however, does not mean every binary will work, and be especially
cautious if it was compiled for a different version of the OS. 
Things to check:
	1) each part of the compiler has enough men (see the chmem man page)
	2) all the files are in the right place (use gcc -v file.c to see as
   	   gcc tries to execute each pass, and see which it fails on)
Many UNIX programs don't ever expect to run out of memory, and don't
handle it very well when they do, so it is always a concern when running
new software under MINIX. (This is not a problem with most of the GNU stuff
that I have used).

Joe Pickert