make release custom kernel conf not found

Rick Miller vmiller at
Mon Jan 30 18:39:13 UTC 2012

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 <rfarmer at> wrote:
> On Sun, Jan 29, 2012 at 9:03 AM, Rick Miller <vmiller at> wrote:
>> Hi All,
>> I am performing a `make release` to build a new release with a custom
>> kernel.  The `make release` fails with the following error:
>> cd /usr/src/release/..;  make TARGET_ARCH=amd64 TARGET=amd64
>> 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:
>> CHROOTDIR=/app/release
>> CVSROOT=/home/cvs
>> EXTPORTSDIR=/usr/ports
>> EXTSRCDIR=/usr/src
>> I am unsure how to get `make release` to realize the location of the
>> kernel config.  Also, 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.  I appreciate any advice and feedback.  Thanks.
> The kernel is built inside the chroot, so all paths are really
> /app/release/<whatever>. 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

Take care
Rick Miller

More information about the freebsd-questions mailing list