Thanks, found it eventually!

* Lagno, DenisX <denisx.lagno@intel.com> [0407 13:07]:
> http://news.gw.com/netbsd.current.users/64313
> 
> > -----Original Message-----
> > From: current-users-owner@NetBSD.org 
> > [mailto:current-users-owner@NetBSD.org]On Behalf Of Patrick Welche
> > Sent: Thursday, April 29, 2004 3:59 PM
> > To: Dick Davies
> > Cc: NetBSD Current
> > Subject: Re: can't build current - gcc fails
> > 
> > 
> > On Thu, Apr 29, 2004 at 12:26:56PM +0100, Dick Davies wrote:
> > > * Patrick Welche <prlw1@newn.cam.ac.uk> [0423 12:23]:
> > > > On Thu, Apr 29, 2004 at 11:38:29AM +0100, Dick Davies wrote:
> > > > > 
> > > > > I'm about to try bumping a 1.6 box to current. I'ts the first
> > > > > build I've applied to it since September, so I thought I'd try 
> > > > > a test build from the same sources on my laptop first.
> > > > > 
> > > > > The kernel built fine - there are some sysctl errors during
> > > > > boot, but I expected those and there's nothing too terminal - 
> > 
> > Maybe it is (!) uname uses sysctl, and is missing the machine type.
> > It should contain info from:
> > 
> > sysctl kern.ostype
> > sysctl kern.hostname
> > sysctl kern.osrelease
> > sysctl kern.version
> > sysctl hw.machine
> > 
> > So, it seems "sysctl hw.machine" isn't working.. (and it's handy for
> > gcc to know what machine it's trying to make executables for ;) )
> > 
> > 
> > > root@dozer:src$ uname -a
> > > NetBSD dozer 2.0E NetBSD 2.0E (DOZER) #1: Thu Apr 29 
> > 09:47:25 BST 2004  \
> > > rasputin@dozer:/usr/obj/sys/arch/i386/compile/DOZER
> > 
> > Cheers,
> > 
> > Patrick
> > 
> 

-- 
Down with categorical imperative!
Rasputin :: Jack of All Trades - Master of Nuns