Current kernel build broken with linuxkpi?

[Emmanuel Vadot]

On Wed, 13 Jan 2021 14:52:32 -0500
Robert Huff <roberthuff at rcn.com> wrote:

> 
> Hans Petter Selasky <hps at selasky.org>:
> 
> >   You need to update that DRM port you are using before the issue
> >   will be fixed.
> 
> 	I'm confused.
> 	I have drm-current-kmod listed in PORTS_MODULES; things on that
> list get built _after_ buildkernel (installkernel??) for reasons I
> thought I understood.
> 	You are telling me I need to update this _before_ buildkernel?
> 
> 
> 			Perplexedly,
> 
> 
> 				Robert Huff
> 

 That's one of the problems of having external kmods.
 drm-current-kmod have the option by default to install it's sources
in /usr/local/sys/ and when doing a make buildkernel those sources are
getting built too.
 One problem is that when, like with the latest update to linuxkpi that
I did, we introduce changes that breaks external kmods, you first need
to upgrade your ports/package (not your ports tree) so the new sources
are updated too and then do a make buildkernel.
 That really sucks but still helps a bit when there isn't conflicted
changes in the source tree but you still need to rebuild your kernel
module.

-- 
Emmanuel Vadot <manu at bidouilliste.com> <manu at freebsd.org>