Subject: Re: Libc problem building current?
To: Chad Mynhier <mynhier@cs.utk.edu>
From: David Brownlee <abs@anim.dreamworks.com>
List: current-users
Date: 01/22/1998 15:37:08
	Did you build a new kernel first?
	You should _always_ build the new kernel before the userland.

		David/absolute

.---- I've been too drunk to love ----.-- I've been too drunk to remember -.
|          too drunk to care          |    the hell of the night before    |
|  looked like death, felt like hell  |   I've been drinking myself blind  |
`------ been the worse for wear ------'-- and still I'll drink some more --'

On Thu, 22 Jan 1998, Chad Mynhier wrote:

> 
> (I'm a newbie at building using -current source, so be gentle.)
> 
> I'm having a problem doing a 'make build' with sources supped as of
> this morning (Jan. 22).  The build goes fine until after libc is 
> installed.  After libc gets installed, the compiler starts getting 
> errors complaining about signal 12 (SIGSYS -- bad argument to system
> call.)
> 
> If I symlink libc.so and libc.so.12 back to libc.so.12.20, I can redo
> the following with no problem (this is where things started to go wrong):
> 
> ( cd /usr/src/gnu/lib && make depend && make && make install )
> 
> Any advice?
> 
> Chad Mynhier
>