modules & options

Joerg Sonnenberger joerg at
Mon Sep 6 01:43:38 PDT 2004

On Sun, Sep 05, 2004 at 02:34:02PM +0200, Sascha Wildner wrote:
> Hi,
> is it on purpose that the modules built with buildkernel do not honor 
> the options in the kernel config?

Yes, because you can build modules outside the normal kernel build directory
and it can't determine which kernel config to use as base.

> If I put 'options VESA_DEBUG' in my kernel config the module vesa.ko 
> won't have this option defined. This is becauses it #includes an empty 
> opt_vesa.h from 
> /usr/obj/usr/src/sys/<KERNCONF>/usr/src/sys/dev/video/i386/vesa (the 
> module build directory) instead of the one in 
> /usr/obj/usr/src/sys/<KERNCONF> (the kernel build directory) which 
> contains the VESA_DEBUG option.
> Is there a way to achieve what I want (kldload vesa but keep debugging 
> output)?

Sure, just copy the opt_vesa.h from your kernel build directory into the
module build directory.


> Regards,
> Sascha
> -- 

More information about the Kernel mailing list