Date: Fri, 27 Oct 2006 11:36:49 +0200 From: "Helmut Schneider" <jumper99@gmx.de> To: <ru@FreeBSD.org>, <freebsd-bugs@FreeBSD.org> Subject: Re: misc/104854: "make release" custom kernel unsuccessful Message-ID: <05ca01c6f9ab$6d8def20$609b65c1@vpe.de> References: <200610270901.k9R91pTp083632@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
From: "Ruslan Ermilov" <ru@FreeBSD.org>
> Synopsis: "make release" custom kernel unsuccessful
>
> State-Changed-From-To: open->closed
> State-Changed-By: ru
> State-Changed-When: Fri Oct 27 08:59:59 UTC 2006
> State-Changed-Why:
> This behavior is by design
Well, then either I do not understand that design, or I do something
completely wrong (if so I appologize):
mkdir ${RD}/kernels
for i in ${KERNELS_BASE} ${KERNELS}; do \
mkdir -p ${RD}/kernels/$${i}; \
done
KERNELS_BASE is set to $MY_CUSTOM_KERNEL.
KERNELS is not mandatory and never set, so it is empty.
=> the only directory which is created is $MY_CUSTOM_KERNEL. The directory
GENERIC will not be created.
# Build boot and install floppies.
floppies.1:
@gzip -9nc ${RD}/kernels/GENERIC/kernel > ${RD}/kernels/kernel.gz
fails.
=> make release fails.
make CHROOTDIR=/home/release CVSROOT=/usr BUILDNAME=6.1-RELEASE
RELEASETAG=RELENG_6_1 EXTPORTSDIR=/usr/ports EXTSRCDIR=/usr/src
KERNELS_BASE=IBM_HS20_SMP NODOC=YES NOPORTS=YES MAKE_ISOS=YES release
Do I have to set KERNELS=$CUSTOM_KERNEL instead of
KERNELS_BASE=$CUSTOM_KERNEL? ("make release" takes ages so I was not able to
test that by now)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?05ca01c6f9ab$6d8def20$609b65c1>