Re: Chicken and egg problem when building (third-party) kernel modules with <bsd.kmod.mk> -- how to solve?

From: John-Mark Gurney <jmg_at_funkthat.com>
Date: Wed, 11 Sep 2013 09:53:46 -0700
Lev Serebryakov wrote this message on Wed, Sep 11, 2013 at 17:37 +0400:
>  It is good idea to set KERNBUILDDIR when build module. But to set it you
> need to know ${.OBJDIR} from ${SYSDIR} and ${SYSDIR} is set in bsd.kmod.mk,
> which should be included last (after defining KERNBUILDDIR).
> 
>  How this loop could be broken?

You don't set it as part of the module Makefile... It is expected that
KERNBUILDDIR is set before invoking the module Makefile, such as when
the module is built as part of the kernel...

If you need to build it stand alone, you still need the opt_*.h files
from the kernel you are going to run it with, and that directory is
what you need to set KERNBUILDDIR...

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."
Received on Wed Sep 11 2013 - 14:53:53 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:41 UTC