From owner-freebsd-stable Mon Jul 29 9:27:40 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35B5937B400 for ; Mon, 29 Jul 2002 09:27:36 -0700 (PDT) Received: from yertle.kciLink.com (yertle.kcilink.com [216.194.193.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC55443E31 for ; Mon, 29 Jul 2002 09:27:35 -0700 (PDT) (envelope-from khera@kciLink.com) Received: from onceler.kciLink.com (onceler.kciLink.com [216.194.193.106]) by yertle.kciLink.com (Postfix) with ESMTP id 33E132178B for ; Mon, 29 Jul 2002 12:27:30 -0400 (EDT) Received: by onceler.kciLink.com (Postfix, from userid 100) id DE36A3D11; Mon, 29 Jul 2002 12:27:29 -0400 (EDT) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: Vivek Khera To: freebsd-stable@freebsd.org Subject: Re: HEADS UP: share/mk stuff is being updated (was: Re: bsd.init.mk ?) Newsgroups: ml.freebsd.stable References: <1026974131.3d3661b3c9a1c@intranet.consol.de> <20020718115138.GB99249@sunbay.com> X-Trace: lorax.kciLink.com 1027959660 79461 216.194.193.106 (29 Jul 2002 16:21:00 GMT) X-Complaints-To: daemon@kciLink.com X-Virus-Scanned: by amavisd-new amavisd-new-20020630 (@kci) X-Razor-id: 61e6785b46f640a795d41309b187ba5c7cb2191a Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> "RE" == Ruslan Ermilov writes: RE> This particular problem is caused by your /usr/share/mk stuff being not RE> in sync with the source tree. To work around this (if you really want RE> to build only your kernel from fresh sources), you need to: RE> cd /usr/src/share/mk && make install RE> Then continue with the kernel build config(8) way. I'm observing a similar problem building the kernel modules from within the vmware2 port. After answering the interactive questions (no bridging, default everything else), I get this: ===> Building for vmware2-2.0.4.1142 ===> vmmon-only make -f Makefile.FreeBSD SMP=YES clean && make -f Makefile.FreeBSD SMP=YES "/sys/conf/kmod.mk", line 63: Could not find bsd.init.mk "/sys/conf/kmod.mk", line 190: Could not find bsd.links.mk make: fatal errors encountered -- cannot continue *** Error code 1 Stop in /u/onceler1/usr/ports/emulators/vmware2/work/vmware-distrib/vmmon-only. *** Error code 1 Stop in /u/onceler1/usr/ports/emulators/vmware2/work/vmware-distrib. *** Error code 1 Stop in /u/onceler1/usr/ports/emulators/vmware2. *** Error code 1 Stop in /u/onceler1/usr/ports/emulators/vmware2. This is with: FreeBSD onceler.kciLink.com 4.6-STABLE FreeBSD 4.6-STABLE #0: Mon Jun 17 23:25:23 EDT 2002 The kernel was built a few hours after the cvsup finished. I used the standard buildworld/kernel installworld/kernel and mergemaster. Running your above make install in the mk directory fixed this issue as well. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message