kernel module options (was ipfw2 broken)
ru at freebsd.org
Thu Aug 19 12:19:35 PDT 2004
On Thu, Aug 19, 2004 at 11:08:40AM -0700, John-Mark Gurney wrote:
> Sean McNeil wrote this message on Thu, Aug 19, 2004 at 10:53 -0700:
> > On Thu, 2004-08-19 at 10:22, Andre Oppermann wrote:
> > > IPDIVERT wasn't compiled into the module before. It's surrounded by
> > > #if !defined(KLD_MODULE). However if the kernel was compiled with option
> > > IPDIVERT but w/o IPFIREWALL is was working anyway.
> > Has this changed? From what I saw yesterday no option in my config file
> > could possibly effect the compilation of the ipfw2 module. The only way
> > I could see doing it was to modify the Makefile for the module. yuk.
> > I would like to see a general mechanism supported to turn on various
> > options within a module build. Would it be possible to fix module
> > building to honor options from the config?
> I had a set of changes a while back that would link all of the opt_*.h
> files in the various module's dirs back to the ones in the main kernel
> compile assuming that there wasn't a specific rule in the Makefile to
> build that file. I.e. 99% of the opt_*.h rules could be eliminated.
> This solution was decided to be inadaquate, and was not accepted, but
> I again propose it. It quick and easy.
And how the standalone module could be built if you eliminated 99% of
opt_*.h rules from module makefiles?
ru at FreeBSD.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20040819/a93a9c09/attachment.bin
More information about the freebsd-current