From owner-freebsd-current  Wed Oct  8 15:56:19 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id PAA20601
          for current-outgoing; Wed, 8 Oct 1997 15:56:19 -0700 (PDT)
          (envelope-from owner-freebsd-current)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA20596
          for <FreeBSD-current@FreeBSD.ORG>; Wed, 8 Oct 1997 15:56:16 -0700 (PDT)
          (envelope-from asami@vader.cs.berkeley.edu)
Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.6/8.7.3) id PAA13398; Wed, 8 Oct 1997 15:56:09 -0700 (PDT)
Date: Wed, 8 Oct 1997 15:56:09 -0700 (PDT)
Message-Id: <199710082256.PAA13398@vader.cs.berkeley.edu>
To: tlambert@primenet.com
CC: chuckr@mat.net, FreeBSD-current@FreeBSD.ORG
In-reply-to: <199710081857.LAA00242@usr05.primenet.com> (message from Terry Lambert on Wed, 8 Oct 1997 18:57:11 +0000 (GMT))
Subject: Re: buildworld
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * Unless you have an if_de.c using ethernet card...

We're not talking about the kernel.  That's not part of "make world".

 * No, you can't, so long as any code anywhere tests __FREEBSD__.

Actually, if that code is part of "make world", it will be built using
the "new" compiler that has __FreeBSD__ defined to the right value.

 * > Do "make installworld" on the NFS clients and you'll be all set (I do
 * > this all the time).
 * 
 * This will work, because the kernel and compiler versions will be correct.

Actually, if you are rebuilding the world AND the kernel on the
fileserver, this won't work, according to what you said above.  (It
will of course work if you build the kernel on the client, but that
always worked.)

Satoshi