Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!mips!cs.uoregon.edu!ogicse!zephyr.ens.tek.com!tektronix!nosun!qiclab!m2xenix!steven
From: steven@m2xenix.psg.com (Steven Furber)
Newsgroups: comp.os.minix
Subject: Re: How to install GCC on MacMinix
Message-ID: <1990Nov14.021835.5614@m2xenix.psg.com>
Date: 14 Nov 90 02:18:35 GMT
References: <627@pdxgate.UUCP> <1990Nov13.165207.5755@cbnewsc.att.com>
Distribution: na
Organization: Pacific Systems Group, Portland Oregon US
Lines: 53

In <1990Nov13.165207.5755@cbnewsc.att.com> ladd@cbnewsc.att.com (david.ladd) writes:

>In article <627@pdxgate.UUCP>, deo@eecs.cs.pdx.edu (Steven Furber) writes:

>[ excellent description of GCC install deleted ]

Thanks.  I was a bit worried that the install wouldn't work, but I see
you hit on some problems I too am finding (with the help of someone else
pointing a couple more out to me...)


>I'm still having problems getting stdio to recognize EOF.  For
>instance,
>	..
>	x = read(0, buf, 1024);
>	write(1,buf,x);
>	..
>works, but
>	..
>	while( (c = getchar()) != EOF )
>		putchar(c);
>	..

>fails to stop at the end of the file.
	
I can't help you with this.  The lib[32]c.a file seems to have quite a
few problems.  I was recently told it was for Minix 1.1 or 1.3, and not
for a current release.  This might be part of the problem (sorry, I'm
pretty new to the more brain busting parts of using computers).

>I've tried to re-build libc32.a from 
>atari.archive.umich.edu:/atari/gnustuff/minix/libsrc.tar.Z
>but I'm having trouble with actually building the archive from 
>the .o's

You'll need to archive them with GNU's ar, not the Minix ar.  Someone
recently sent me mail saying they either had the sources or had the
sources and ar running.  Even if you do recompile all of the libraries,
you need to figure out what to do with the MacMINIX system specific
stuff (ie: header files).

I ran into a problem when using memcpy(..).  It turns out the library
knows memccpy(..), yet the header file specified memcpy(..).  Before I
realized that it wanted memccpy(..) something I did to fix it was to
compile /usr/src/lib/ansi/memcpy.c with GCC and then link it into my
file.  It worked, and it may work for other problems.
GCC also has problems with stdout being used with fprintf, and I think
printf too.  I know I had problems when trying something someone else
suggested.

Right now I'm only using GCC when I've got something that requires ANSI
C.  Until we can get it up and running for the Mac and MacMinix 1.5,
it's going to need tobe handled with extreme care.