Date: Thu, 28 May 2020 13:48:49 -0700
From: "Greg A. Woods" <[email protected]>
Message-ID: <[email protected]>
| So, now what? Where else should I look to debug this mess?
Compare mk.conf (or some other place in your build setup) on the system
that built OK, and the one that didn't - I'm guessing that the latter has
LOCKDEBUG set.
| I'm guessing they are formed either with merging operator (##) in a
| macro somewhere, but where, and how do I find it without carefully
| reading everything related?
Rump does a lot of that - it includes kernel source files, and fiddles
with the names.
Unless you're desperate for a masochist experience, I'd stay way the hell
away from it - just work out what you need to fiddle to make things build.
At another guess, only define LOCKDEBUG if _KERNEL is defined (don't let
it be set in rump, which while using kernel sources, isn't kernel).
kre
