Date: Wed, 27 Dec 2017 11:20:18 +1100 (EST) From: Dave Horsfall <dave@horsfall.org> To: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Of LSOF Message-ID: <alpine.BSF.2.21.1712271111260.27626@aneurin.horsfall.org> In-Reply-To: <4DB6D455-3F50-4AC9-83A4-0AFD06B6058C@FreeBSD.org> References: <alpine.BSF.2.21.1712271008040.27626@aneurin.horsfall.org> <4DB6D455-3F50-4AC9-83A4-0AFD06B6058C@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 27 Dec 2017, Dimitry Andric wrote: > Binary packages are built on the oldest supported 10.x release, which > currently is 10.3. I think that lsof is just one of the few programs > that care about this, and show a warning. This is probably because lsof > pokes around in half-documented (or undocumented) system structures, > which might change even in minor releases. Thanks for that. > The path of lowest resistance is to ignore the warning, otherwise build > (or package) the port yourself. Which I discovered last year required that kernel sources be installed (which I didn't have at the time; I didn't build this system) because it wanted a certain #include file. I reported this in a PR saying that perhaps all header files be shipped, but I dunno what happened. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.21.1712271111260.27626>