Date: Wed, 13 Jan 2021 21:42:49 +0100 From: Emmanuel Vadot <manu@bidouilliste.com> To: Robert Huff <roberthuff@rcn.com> Cc: current@freebsd.org, Hans Petter Selasky <hps@selasky.org> Subject: Re: Current kernel build broken with linuxkpi? Message-ID: <20210113214249.8930e6d8c6884dba3b68c776@bidouilliste.com> In-Reply-To: <24575.20352.153922.53339@jerusalem.litteratus.org> References: <3c0d77d7-6b99-d48e-6e8a-92134b2fac7e@selasky.org> <24575.20352.153922.53339@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 13 Jan 2021 14:52:32 -0500 Robert Huff <roberthuff@rcn.com> wrote: > > Hans Petter Selasky <hps@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@bidouilliste.com> <manu@freebsd.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210113214249.8930e6d8c6884dba3b68c776>