In general it's not a concern if someone is building LKM's for themself.

However, considering the snapshot/release though, which version should end
up in there? The sun3X LKM's probably won't work under certain conditions on
a sun3 and should be labeled accordingly. We already ship a GENERIC and 
GENERIC3X kernel so I'd lean towards changing the lkm builds to build both
sun3 and sun3x versions.

(BTW: the _LKM section in vmparam.h was already there. I was just expanding it
in this case. The problem, is _LKM is all over the source tree in some places
because the kernel is structured monolithically and we're trying to wedge 
modules into that.)

James


>In <200102041016.MAA02711@netbsd.hut.fi>
>jmc@netbsd.org wrote:
>
>> Module Name:	syssrc
>> Committed By:	jmc
>> Date:		Sun Feb  4 10:16:03 UTC 2001
>> 
>> Modified Files:
>> 	syssrc/sys/arch/sun3/include: vmparam.h
>> 
>> Log Message:
>> In the LKM section add some things the LKM's need (since they aren't
>> defining _SUN3_ or _SUN3X_ generally to pickup the full vmparam.h
>> 
>> Added MAXDSIZ (set to sun3's limit) and VM_NFREELIST
>
>Generating assym.h from genassym.cf under lkm/compat directories
>also requires -D_SUN3_ or -D_SUN3X_.
>(It fails but does not cause error..)
>
>I'd like to add
>
>.if (${MACHINE} == "sun3")
>CPPFLAGS+=-D_SUN3_
>.endif
>
>to sys/lkm/compat/Makefile.inc rather than putting
>"#if defined(_LKM)" to each header files.
>
>Comments?
>---
>Izumi Tsutsui
>tsutsui@ceres.dti.ne.jp
>
>
>
>