Doug White wrote:
On Thu, 4 Sep 2003, John Birrell wrote:
however kern.post.mk only uses KERNEL_KO, so even though config(8) has
set KERNEL for me, that name only gets used for the boot directory.
There doesn't seem to be any way of getting KERNEL_KO set from the
kernel config file.
If you chan
On Wed, Sep 03, 2003 at 09:22:09PM -0700, Doug White wrote:
> On Thu, 4 Sep 2003, John Birrell wrote:
>
> > however kern.post.mk only uses KERNEL_KO, so even though config(8) has
> > set KERNEL for me, that name only gets used for the boot directory.
> > There doesn't seem to be any way of getting
On Thu, Sep 04, 2003 at 12:31:33PM +0200, Dag-Erling Sm?rgrav wrote:
> I have
>
> Index: kern.pre.mk
> ===
> RCS file: /home/ncvs/src/sys/conf/kern.pre.mk,v
> retrieving revision 1.34
> diff -u -r1.34 kern.pre.mk
> --- kern.pre.mk 22
John Birrell <[EMAIL PROTECTED]> writes:
> It would make more sense to me if kern.pre.mk contained this:
>
> KERNEL?= kernel
> KERNEL_KO?= ${KERNEL}
> KODIR?= /boot/${KERNEL}
>
> Comments?
I have
Index: kern.pre.mk
=
On Thu, 4 Sep 2003, John Birrell wrote:
> however kern.post.mk only uses KERNEL_KO, so even though config(8) has
> set KERNEL for me, that name only gets used for the boot directory.
> There doesn't seem to be any way of getting KERNEL_KO set from the
> kernel config file.
If you change the name
In a RELENG_4 kernel build, I'm accustomed to setting 'config foo' in
a kernel configuration file and ending up with a kernel called 'foo'.
In current, kern.pre.mk contains:
KERNEL_KO?= kernel
KERNEL?=kernel
KODIR?= /boot/${KERNEL}
however kern.post.mk only uses KERNEL_KO, so
