package options

[Iain Hibbert <plunky%rya-online.net@localhost> See http://spamassassin.org/tag/ for more details. Report problems to http://sf.net/tracker/?func=add&group_id=1&atid=200001]

Hi,
   Had a thought - the package wip/lzs-lkm that I am currently waiting on
something for creates a Loadable Kernel Module for NetBSD (net/mppe-lkm
and security/pflkm also do that)

There is a problem with LKM's in NetBSD, in that if the kernel is compiled
with certain flags (option DIAGNOSTIC at least, not sure about any others)
then a LKM will not load unless it also used -DDIAGNOSTIC because some
system structures apparently change size in that case.

"make CFLAGS=-DDIAGNOSTIC" does work, but I thought I if I made something
generic like

PKG_OPTIONS.lkm=        diagnostic

then the end user can specify that and all kernel modules will get built
correctly. This works for my package but for security/pflkm at least uses
its own PKG_OPTIONS_VAR=PKG_OPTIONS.pf and I'm not sure how to integrate
that with PKG_OPTIONS.lkm - can a package read two PKG_OPTIONS settings?

So, not sure that its a great idea in any case but how to proceed? (any
example packages I should look at?)

iain


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
pkgsrc-wip-discuss mailing list
pkgsrc-wip-discuss%lists.sourceforge.net@localhost
https://lists.sourceforge.net/lists/listinfo/pkgsrc-wip-discuss