From owner-freebsd-stable@freebsd.org Tue Dec 13 00:12:50 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 48420C73027 for ; Tue, 13 Dec 2016 00:12:50 +0000 (UTC) (envelope-from herbert@mailbox.org) Received: from mx1.mailbox.org (mx1.mailbox.org [80.241.60.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.mailbox.org", Issuer "SwissSign Server Silver CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0F2A615EE for ; Tue, 13 Dec 2016 00:12:49 +0000 (UTC) (envelope-from herbert@mailbox.org) Received: from smtp1.mailbox.org (smtp1.mailbox.org [80.241.60.240]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.mailbox.org (Postfix) with ESMTPS id 2EB9543C8F for ; Tue, 13 Dec 2016 01:12:47 +0100 (CET) X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp1.mailbox.org ([80.241.60.240]) by spamfilter02.heinlein-hosting.de (spamfilter02.heinlein-hosting.de [80.241.56.116]) (amavisd-new, port 10030) with ESMTP id 2PYFFoZb4y7T for ; Tue, 13 Dec 2016 01:12:45 +0100 (CET) Date: Tue, 13 Dec 2016 01:12:43 +0100 Message-ID: <86r35cptz8.wl-herbert@mailbox.org> From: "Herbert J. Skuhra" To: Subject: Re: make buildkernel does not respect KERNCONF or JOBS in /etc/make.conf In-Reply-To: References: <201612120138.uBC1cA59025994@sdf.org> <86r35dd46x.wl-herbert@mailbox.org> <9B.7B.16304.3F86E485@dnvrco-omsmta02> <15672f53-1a34-3120-0aa8-03aa6401be54@zyxst.net> MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2016 00:12:50 -0000 Kevin Oberman skrev: > = > On Mon, Dec 12, 2016 at 1:16 AM, tech-lists wr= ote: >> On 12/12/2016 09:07, Thomas Mueller wrote: >> = >>> My question is, do you build modules redundantly, or just once? >>> I don't want to build the same modules more than once. >>> = >> = >> For me - redundantly, I guess. It's not like it takes a lot of time = or >> space on the compiling machine, and I ensure that everything that ne= eds to >> be built, is built. >> = >> PUMPKIN =3D heavily modified config with all the stuff I don't need = stripped >> out, and a couple of non-default lines. >> = >> GENERIC =3D unmodified kernel that should work if by some chance PUM= PKIN >> doesn't. >> -- >> J. > = > = > Clearly the documentation is a bit behind the times. For some time pe= ople > have used KERNCONF to build multiple kernels, but that was a lucky th= ings > that was not officially supported. It just happened to work. Then, wi= th > 11.0, it no longer did in many cases sue to changes in the kernel bui= ld > system. When people complained, there did not seem to be a way to fix= this > without blocking future goals in speeding up and enhancinghte standar= d > kernel build. > = > The result was BUILDKERNELS. It was specifically designed to allow th= e > building of multiple kernels and the appropriate modules. This would = always > take longer and use more disk space, but it would work reliably. Now,= bit > building a single, local kernel, KERNCONF is the best way, though I s= uspect > that it make only a small difference until new capabilities are added= later > in the life of 11. > = > So, while it seems the man pages need to catch up, building multiple > kernels should be done with KERNCONF in either make.conf or src.conf = and > multiple kernels with BUILDKERNELS. ??? From=20/usr/src/Makefile.inc1: 1137 .if ${TARGET_ARCH} =3D=3D "powerpc64" 1138 KERNCONF?=3D GENERIC64 1139 .else 1140 KERNCONF?=3D GENERIC 1141 .endif [...] 1151 .if defined(NO_INSTALLKERNEL) 1152 # All of the BUILDKERNELS loops start at index 1. 1153 BUILDKERNELS+=3D dummy 1154 .endif 1155 .for _kernel in ${KERNCONF} 1156 .if exists(${KERNCONFDIR}/${_kernel}) 1157 BUILDKERNELS+=3D ${_kernel} 1158 .if empty(INSTALLKERNEL) && !defined(NO_INSTALLKERNEL) 1159 INSTALLKERNEL=3D ${_kernel} 1160 .endif 1161 .endif 1162 .endfor So setting BUILDKERNELS has no effect. -- Herbert