Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!spool.mu.edu!news.cs.indiana.edu!ariel.unm.edu!triton.unm.edu!sfreed
From: sfreed@triton.unm.edu (Steven Freed CIRT)
Newsgroups: comp.os.minix
Subject: Re: ok
Message-ID: <1991Jun28.035353.11793@ariel.unm.edu>
Date: 28 Jun 91 03:53:53 GMT
References: <13990@mentor.cc.purdue.edu>
Organization: University of New Mexico, Albuquerque
Lines: 46

In article <13990@mentor.cc.purdue.edu> asg@sage.cc.purdue.edu (The Grand Master) writes:
>Problems still:
>I got kernel to compile by replacing sigaddset, sigismember, sigdelset,
>and sigemptyset with the corresponding lines from the 1.5.10 kernel
>(this occurs in system.c).

Like I said in reply to someone elses plight.... You need to get the 
additional libs from whereever you got the update patches.

>Is there anyone out there who got 1.6.16 to compile using the plain
>1.5.10 compiler??

Just finished compiling, will start testing in about an hour.

>Three weeks I have been trying to compile 1.6.16
>If I do not get it straight soon, I am going to delete 1.6.16 and just
>live with 1.5.10.
>When is 2.0 due out???

***Flame ON
Whoa!!! 1.6.16 is *BETA* !!!! If you want to play with it, you must
expect the frustrations that come with with beta software. If you want
to install it with a minimal amount of hassle then wait for the
full release to come out. If you want a smooth clean install, go 
buy a Sun with the OS already installed on it. 

Sure, as long as we are trying to compile these updates with the old
compiler and libs, there are going to be a few problems. The 2.0 C
compiler, according to Andy is coming "soon". I can understand his 
reluctance to be pinned down to a specific date, but believe me, it 
will be soon. None the less, almost all the problems can be worked around
with the sources that are available and a little creativity and 
effort. If you can't deal with this, then go back to 1.5.10 and
wait.

***Flame OFF

No, I am not going to elaborate any further on how I got everything
to compile untill I've tested it to make sure it works. I really don't
want to feel responsible for trashing my disk *and* someone elses
because of something I posted. To give a hint, however, I edited 
about 70 of the libc.a source files.

-- 

Steve.                    sfreed@ariel.unm.edu