From owner-freebsd-doc@FreeBSD.ORG Fri Jun 21 21:38:57 2013 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 723171C3 for ; Fri, 21 Jun 2013 21:38:57 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from mail.jr-hosting.nl (mail.jr-hosting.nl [78.47.69.234]) by mx1.freebsd.org (Postfix) with ESMTP id 362AD1753 for ; Fri, 21 Jun 2013 21:38:57 +0000 (UTC) Received: from [10.0.2.17] (a44084.upc-a.chello.nl [62.163.44.84]) by mail.jr-hosting.nl (Postfix) with ESMTPSA id 431D838B3540; Fri, 21 Jun 2013 23:38:47 +0200 (CEST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: broken instructions for buildkernel From: Remko Lodder In-Reply-To: <02c901ce6dec$1b330140$519903c0$@hain-global-consulting.com> Date: Fri, 21 Jun 2013 23:38:46 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <8C5019CC-4959-40D5-B017-6F19E4CBD959@FreeBSD.org> References: <023e01ce6d47$dab08470$90118d50$@hain-global-consulting.com> <02c901ce6dec$1b330140$519903c0$@hain-global-consulting.com> To: Tony Hain X-Mailer: Apple Mail (2.1508) Cc: doc@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jun 2013 21:38:57 -0000 On Jun 20, 2013, at 9:26 PM, Tony Hain = wrote: > Thanks Adam.=20 >=20 > I had been on the page you sent for the 9.0 to 9.1 upgrade of this = machine. > My intent was not to upgrade the machine to 10.0, at this point it was = just > to build the kernel for a new VM. Granted I am not the most engrained = in > FreeBSD procedures, but to me that leads to the "building a kernel" = page.=20 >=20 >=20 >=20 > While buildworld may not be a declared prereq, something in that = process > "fixes" a missing definition. No matter which distro of 10.0 I tried = to > build it would always exit on a missing prototype for yyparse, but = after > buildworld it just ran to completion. That sounds like a prereq to = me... > Even if it is not, a hint on one or both of the pages that reference > building a kernel, about yyparse failures being fixed by buildworld = would > save people frustration and time. If I was the first to stumble over = this, I > wouldn't have been able to find discussion about it on the web, and = still > wouldn't know how to fix it.=20 >=20 If you read the documentation link that Adam send you specifically on = this page: http://www.freebsd.org/doc/handbook/makeworld.html =20 it is demonstrated and advised why things happen: =95 make buildworld This first compiles the new compiler and a few related tools, then uses = the new compiler to compile the rest of the new world. The result ends = up in /usr/obj. =95 make buildkernel This uses the new compiler residing in /usr/obj in order to protect = against compiler-kernel mismatches. if you upgrade from x to y (9 to 10 in this case) you must be sure that = the toolchain and buildtools are up to date, thus you need to make = buildworld even though you do not plan on using it (note that you might get different results = then you might expect, world and kernel needs to be aligned up as = possible to ensure that they understand eachother). There is no need to adjust the documentation for the specific yyparse = step, in the tuture there will be other things that break if people do = not follow the rules described. Thanks Remko --=20 /"\ With kind regards, | remko@elvandar.org \ / Remko Lodder | remko@FreeBSD.org X FreeBSD | = http://www.evilcoder.org / \ The Power to Serve | Quis custodiet ipsos custodes