From owner-cvs-src@FreeBSD.ORG Fri Apr 6 17:17:54 2007 Return-Path: X-Original-To: cvs-src@freebsd.org Delivered-To: cvs-src@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D209916A403; Fri, 6 Apr 2007 17:17:54 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.freebsd.org (Postfix) with ESMTP id 84FBC13C459; Fri, 6 Apr 2007 17:17:54 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id 42FFA627E; Fri, 6 Apr 2007 21:17:53 +0400 (MSD) Received: from edoofus.park.rambler.ru (unknown [81.19.65.108]) by relay0.rambler.ru (Postfix) with ESMTP id 13ACC6252; Fri, 6 Apr 2007 21:17:53 +0400 (MSD) Received: (from ru@localhost) by edoofus.park.rambler.ru (8.13.8/8.13.8) id l36HHEEB084842; Fri, 6 Apr 2007 21:17:14 +0400 (MSD) (envelope-from ru) Date: Fri, 6 Apr 2007 21:17:14 +0400 From: Ruslan Ermilov To: Kip Macy Message-ID: <20070406171714.GA84721@rambler-co.ru> References: <200704060605.l3665jcT032027@repoman.freebsd.org> <20070406064751.GE29457@rambler-co.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tKW2IUtsqtDRztdT" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.14 (2007-02-12) X-Virus-Scanned: No virus found Cc: cvs-src@freebsd.org, src-committers@freebsd.org, Kip Macy , cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/modules Makefile X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Apr 2007 17:17:54 -0000 --tKW2IUtsqtDRztdT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Fri, Apr 06, 2007 at 10:03:30AM -0700, Kip Macy wrote: > Ok, how do I fix this? "make kernel-toolchain"? I'll back it out as > soon as UPDATING is updated with the appropriate action - magic flags > aren't an appropriate response. >=20 In this particular case, a simple "make buildkernel" will suffice, i.e. you don't need kernel-toolchain. In the general case, if you don't know the specifics of the changes, both kernel-toolchain and buildkernel are required. All info is already in src/UPDATING: : COMMON ITEMS: [...] : To build a kernel : ----------------- : If you are updating from a prior version of FreeBSD (even one just : a few days old), you should follow this procedure. It is the most : failsafe as it uses a /usr/obj tree with a fresh mini-buildworld, :=20 : make kernel-toolchain : make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=3DYOUR_KERNEL_HERE : make -DALWAYS_CHECK_MAKE installkernel KERNCONF=3DYOUR_KERNEL_HERE Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --tKW2IUtsqtDRztdT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iD8DBQFGFoCaqRfpzJluFF4RAh+4AJ9Nhv56YKg1bSC1VyvCBcaMhbux5wCfXnZY WpVHuOoz1FaUfLj4vxpufSQ= =R3ED -----END PGP SIGNATURE----- --tKW2IUtsqtDRztdT--