summaryrefslogtreecommitdiff
path: root/net/netbsd-tap/DESCR
diff options
context:
space:
mode:
authorcube <cube@pkgsrc.org>2005-02-20 21:50:57 +0000
committercube <cube@pkgsrc.org>2005-02-20 21:50:57 +0000
commit0c09c0588f99ab5fceeda72a46226d871d6122b3 (patch)
tree84b5cc8d13f54864f68007bdcbe276e1b0ec1d23 /net/netbsd-tap/DESCR
parent90d0b1a41ea6e97e41de3e95be9afe67edf5ba92 (diff)
downloadpkgsrc-0c09c0588f99ab5fceeda72a46226d871d6122b3.tar.gz
o Add a way to pass special definitions to the compilation, to match kernel
environment, and document it in DESCR by lack of a better place. o Fix a reference to local in (yet unused) bl3.mk file. Both issues reported by Hubert Feyrer.
Diffstat (limited to 'net/netbsd-tap/DESCR')
-rw-r--r--net/netbsd-tap/DESCR8
1 files changed, 8 insertions, 0 deletions
diff --git a/net/netbsd-tap/DESCR b/net/netbsd-tap/DESCR
index 28cf9ab2d5b..5c5e80c5c59 100644
--- a/net/netbsd-tap/DESCR
+++ b/net/netbsd-tap/DESCR
@@ -8,3 +8,11 @@ allows an application to read and inject Ethernet frames into the network
stack. tap(4) devices can be created and used individually for system-wide
configurations, but an application can also use a special clonable device
node to create interfaces on demand.
+
+As a LKM must be compiled with the same environment as the kernel with respect
+to a handful of definition (DEBUG, DIAGNOSTIC, MULTIPROCESSOR, LOCKDEBUG and
+MALLOCLOG), the package provides a variable, TAP_KERNEL_ENV, to hold the
+correct addition to the compilation command line. For example, you might want
+to define it the following way in mk.conf:
+
+ TAP_KERNEL_ENV= -DDIAGNOSTIC -DMULTIPROCESSOR