Date: Sat, 03 Mar 2012 22:37:40 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Doug Barton <dougb@FreeBSD.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r232473 - in head: share/mk sys/conf Message-ID: <4F528F24.5040909@FreeBSD.org> In-Reply-To: <4F5278F8.2020109@FreeBSD.org> References: <201203031858.q23IwGvG096048@svn.freebsd.org> <4F5278F8.2020109@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2012-03-03 21:03, Doug Barton wrote: > On 03/03/2012 10:58, Dimitry Andric wrote: >> However, since it is apparently an expected use case to build using old >> .mk files, > > Expected how? It shouldn't happen if you're building in /usr/src. No, but it apparently happens if you build kernel modules separately, or via ports. Or if you build kernel modules for head from older branches. > Wouldn't it be better to track down the real bug? Obviously that would be better, but I received several private messages from people that were annoyed that I "broke" their kernel module builds, and expected me to fix it. There was also at least one such posting on freebsd-current@, where somebody's nvidia-driver port fell over due to my change. I did think about adding a fatal error message to each of the kern.mk files that includes bsd.own.mk, but you can't really do a full sanity check until you add some sort of version number to the bsd.*.mk files.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F528F24.5040909>