From owner-freebsd-current@freebsd.org Wed Oct 21 03:55:15 2015 Return-Path: Delivered-To: freebsd-current@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 74ACFA19EBD for ; Wed, 21 Oct 2015 03:55:15 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-5.mit.edu (dmz-mailsec-scanner-5.mit.edu [18.7.68.34]) by mx1.freebsd.org (Postfix) with ESMTP id 2448ECC7 for ; Wed, 21 Oct 2015 03:55:14 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074422-f79976d0000078ca-82-56270c9bc14b Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id 90.28.30922.B9C07265; Tue, 20 Oct 2015 23:55:08 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id t9L3t7pt023907 for ; Tue, 20 Oct 2015 23:55:07 -0400 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id t9L3t4jn023411 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Tue, 20 Oct 2015 23:55:07 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id t9L3t4iS021412; Tue, 20 Oct 2015 23:55:04 -0400 (EDT) Date: Tue, 20 Oct 2015 23:55:04 -0400 (EDT) From: Benjamin Kaduk To: freebsd-current@freebsd.org Subject: Re: is building kernel in /sys/amd64/conf depreciated in 11 ? In-Reply-To: <20151020164013.GA43495@potato.growveg.org> Message-ID: References: <20151020164013.GA43495@potato.growveg.org> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrCIsWRmVeSWpSXmKPExsUixG6nrjuHRz3M4OBKJos5bz4wOTB6zPg0 nyWAMYrLJiU1J7MstUjfLoEr4/DOT2wFPbwVx19fZm1gXMbVxcjBISFgInHzqmkXIyeQKSZx 4d56NpCwkMBiJondaV2MXEDmZUaJ2fNnskI4T5gkpk+6zgLhNDBKtN68yQrSzSKgLTH5VBeY zSagIjHzzUY2EFtEQF7i2afrYHFhATeJm2cPMoPYnAIWEsvu9zCC2LwCjhKHzsxlgdhsLrG7 NQMkLCqgI7F6/xQWiBJBiZMzn4DZzAJaEsunb2OZwCgwC0lqFpLUAkamVYyyKblVurmJmTnF qcm6xcmJeXmpRbqmermZJXqpKaWbGMGB56K0g/HnQaVDjAIcjEo8vB8WqoUJsSaWFVfmHmKU 5GBSEuVN4lAPE+JLyk+pzEgszogvKs1JLT7EKMHBrCTCe/IaUDlvSmJlVWpRPkxKmoNFSZx3 0w++ECGB9MSS1OzU1ILUIpisDAeHkgTvHS6goYJFqempFWmZOSUIaSYOTpDhPEDDwWp4iwsS c4sz0yHypxgVpcR534IkBEASGaV5cL3gxLCbSfUVozjQK8K8wdxAVTzApALX/QpoMBPQ4IWP VEEGlyQipKQaGKtEH3IGWS06u3362Q2FSq8/5L4vrPrz3y7xrfOGlWskd8k9P6giFizGuJH3 4r819j++f9vfe8ZsqaNe9T0dlnQDjcndJV8qyufvn+n2zXRHaHx/Nk+VX+CvXVN8q58fXFr7 eW3DCfPwyATO+jbVxSKvnN9vy2XeeCln02ou97DHN7b5R09J+67EUpyRaKjFXFScCADXaMmO 5wIAAA== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Oct 2015 03:55:15 -0000 On Tue, 20 Oct 2015, John wrote: > Hi, > > as subject - is building kernel in /sys/amd64/conf depreciated? > > I can get a modified kernel to build and install in /usr/src but not > in /sys/amd64/conf. I always used to be able to do this in there, then > again I either used -RELEASE or -STABLE. I used to do it like this: > > 1. cd /sys/amd64/conf > 2. cp GENERIC MYKERNEL > 3. [make changes to MYKERNEL and save] > 4. config MYKERNEL > 5. cd ../compile/MYKERNEL > 6. make cleandepend && make depend && make > > This fails *every time* during make. It fails at this point: > > Make[1]: "/storage/usr/ports/Mk/bsd.port.mk" line 1204: UNAME_r Why is your kernel build pulling in bsd.port.mk? Please post src.conf and make.conf. > (11.0-CURRENT) and OSVERSION () do not agree on major version number. > *** [all] Error code 1 > make: stopped in /storage/usr/src/sys/amd64/compile/PUMPKIN > The error still happens if I refresh all my sources, build a new world > with a generic kernel and reboot and then try the old method again. > > I *can* build a custom kernel if I cd into /usr/src and do > > 1. make buildkernel KERNCONF=MYKERNEL > 2. make installkernel KERNCONF=MYKERNEL > > Basically I'm asking is this change of behaviour documented and/or am > I doing it wrong? This is not exactly an answer to your question, but buildkernel has been the preferred way to build a kernel for at least four major releases. The manual-config method has limped along because enough of the old-guard of committers has it in finger memory, but manual-config has been excised from the handbook for quite some time. -Ben