From owner-freebsd-questions@FreeBSD.ORG Mon Jan 30 18:39:13 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 75DC0106566C for ; Mon, 30 Jan 2012 18:39:13 +0000 (UTC) (envelope-from vrwmiller@gmail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id C4FA38FC14 for ; Mon, 30 Jan 2012 18:39:12 +0000 (UTC) Received: by wibhn14 with SMTP id hn14so5413759wib.13 for ; Mon, 30 Jan 2012 10:39:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ygpkCZSVb2tNDgG/Yx8szV0LgqkNwhzrLFp5ISf9QI0=; b=l25pv0of8MtCRWLZg0UvGnaAE/J24QYOjDP2RY4vQK0bOuoluTotVvABHZnY23sbCU XMex92/l+kuFjFK27Do2AMhcBjbXUqE14JlfSJw/pbf7OFrVWRWf5dzY0CVAney7mRUZ l/MkmiUX3nHh1hZAObD3/TWV3DsahFcknTS/4= MIME-Version: 1.0 Received: by 10.180.83.72 with SMTP id o8mr29748230wiy.22.1327948751690; Mon, 30 Jan 2012 10:39:11 -0800 (PST) Sender: vrwmiller@gmail.com Received: by 10.227.143.140 with HTTP; Mon, 30 Jan 2012 10:39:11 -0800 (PST) In-Reply-To: References: Date: Mon, 30 Jan 2012 13:39:11 -0500 X-Google-Sender-Auth: 8FwlHT92OHNNBucSe8CdBNj9W7Q Message-ID: From: Rick Miller To: Rob Farmer Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-questions@freebsd.org Subject: Re: make release custom kernel conf not found X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2012 18:39:13 -0000 Thanks Rob... I put the kernel conf file in the source tree as opposed to linking to it and it certainly did compile the custom kernel. What confuses me (not that I expect you to have the answer) is that Chapter 9 of the handbook has a tip that recommends keeping the kernel config in /root/kernels and symlinking to it from the source tree. If it doesn't work, why is there a tip recommending this practice? On Sun, Jan 29, 2012 at 10:14 PM, Rob Farmer wro= te: > On Sun, Jan 29, 2012 at 9:03 AM, Rick Miller w= rote: >> Hi All, >> >> I am performing a `make release` to build a new release with a custom >> kernel. =A0The `make release` fails with the following error: >> >> cd /usr/src/release/..; =A0make TARGET_ARCH=3Damd64 TARGET=3Damd64 >> KERNCONF=3DMYKERNEL kernel =A0DESTDIR=3D/R/stage/kernels KODIR=3D/MYKERN= EL >> ERROR: Missing kernel configuration file(s) (MYKERNEL). >> *** Error code 1 >> >> Stop in /usr/src. >> *** Error code 1 >> >> Stop in /usr/src. >> *** Error code 1 >> >> Stop in /usr/src/release. >> + umount /dev >> *** Error code 1 >> >> Stop in /usr/src/release. >> >> I have the kernel config at /root/kernels/MYKERNEL and >> /usr/src/sys/amd64/conf/MYKERNEL is a symlink to the kernel config. >> The applicable environment variables are set in my .profile as >> follows: >> >> BUILDNAME=3D8.2-RELEASE-MYKERNEL-1.1 >> CHROOTDIR=3D/app/release >> CVSROOT=3D/home/cvs >> EXTPORTSDIR=3D/usr/ports >> EXTSRCDIR=3D/usr/src >> KERNELS=3D"GENERIC MYKERNEL" >> MAKE_DVD=3DYES >> NODOC=3DYES >> NO_FLOPPIES=3DYES >> >> I am unsure how to get `make release` to realize the location of the >> kernel config. =A0Also, I notice that in the command to make the kernel, >> DESTDIR is set to /R/stage/kernels while the CHROOTDIR (and the >> location where I want the release to be built) is /app/release. >> >> I am wondering if someone knows how I may resolve the issue so I can >> get the release built. =A0I appreciate any advice and feedback. =A0Thank= s. >> > > The kernel is built inside the chroot, so all paths are really > /app/release/. Your symlink points to > /app/release/root/kernels/MYKERNEL. It will be easiest to get rid of > the symlink and copy the actual file into your EXTSRCDIR before > starting the make release; alternately you could use the LOCAL_PATCHES > or LOCAL_SCRIPT variables to import it. > > -- > Rob Farmer --=20 Take care Rick Miller