Sometimes it's necessary to build a new config before building a new
kernel.  FYI...

-----Original Message-----
From: Wolfgang Rupprecht <wolfgang@wsrcc.com>
To: port-i386@netbsd.org <port-i386@netbsd.org>
Date: Monday, September 28, 1998 1:22 PM
Subject: Re: Oops.


>seebs@plethora.net (Peter Seebach) writes:
>> I guess I built in the wrong order.  cc gets signal 12 if I put in
the
>> new libc.  Do I need a newer kernel first?

>I'm playing this game as we speak.  I'm upgrading from netbsd-current
>of Aug 20.  I rebuilt in this order: .
>
>    kernel (new signals)
>    libc   (new signals)
>    xlint  (one of the kafs *.ln didn't build)
>    xinstall (needed for new '-p' option)
>    touch get_tk_something.ln in libkafs  (still didn't build; screw
it)
>    gnu/*   (fails in g++/std)
>    / full tree -- make -k
>    / full tree -- make -k install
>    gnu/* -- make -k
>    gnu/* -- make -k install
>    gnu/* -- make -k
>    gnu/* -- make -k install
>    gnu/* -- make -k
>    gnu/* -- make -k install