Any suggestions what to do in the short term about these kvm-grovellers?
lsof isn't so important, the only port depending on it is a tor connection
monitor thingy, libgtop2 affects more things, but the fix is likely to be
the same for both.
In file included from /usr/include/uvm/uvm.h:42,
On 2016/09/20 14:22, Stuart Henderson wrote:
> Any suggestions what to do in the short term about these kvm-grovellers?
> lsof isn't so important, the only port depending on it is a tor connection
> monitor thingy, libgtop2 affects more things, but the fix is likely to be
> the same for both.
>
>
> Any suggestions what to do in the short term about these kvm-grovellers?
> lsof isn't so important, the only port depending on it is a tor connection
> monitor thingy, libgtop2 affects more things, but the fix is likely to be
> the same for both.
the rather ugly solution may be to link that tree
On 2016-09-20, Stuart Henderson wrote:
> Any suggestions what to do in the short term about these kvm-grovellers?
I move that we delete lsof. It has been building fine on the
amd64.ports machines and I was mystified how this could be until I
realized that it uses /usr/src/sys and I hadn't updat
On 2016/09/20 19:40, Christian Weisgerber wrote:
> On 2016-09-20, Stuart Henderson wrote:
>
> > Any suggestions what to do in the short term about these kvm-grovellers?
>
> I move that we delete lsof. It has been building fine on the
> amd64.ports machines and I was mystified how this could be
