Re: lock order reversal

2018-02-26 Thread Chris H
On Mon, 26 Feb 2018 08:42:14 +0200 "Andriy Gapon" said On 26/02/2018 07:18, Jon Brawn wrote: > Wotcha! > > So, I’ve been using FreeBSD 12-CURRENT at various svn releases for a while > now, and I get quite a few “lock order reversal” dumps. The one I’ve got > on my screen at the moment is for

Errors compiling LLVM on RPi3 at 330019

2018-02-26 Thread bob prohaska
At revision 330019 -DNO_CLEAN buildworld stops with --- Target/X86/X86ISelDAGToDAG.o --- /usr/src/contrib/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:2463:7: error: use of undeclared identifier 'SelectCode' SelectCode(ZextTarget.getNode()); ^ /usr/src/contrib/llvm/lib/Target/X86/X86ISelDA

Re: Errors compiling LLVM on RPi3 at 330019

2018-02-26 Thread Dimitry Andric
On 26 Feb 2018, at 16:23, bob prohaska wrote: > > At revision 330019 -DNO_CLEAN buildworld stops with > > --- Target/X86/X86ISelDAGToDAG.o --- > /usr/src/contrib/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:2463:7: error: use > of undeclared identifier 'SelectCode' > SelectCode(ZextTarget.getNo

Re: update of graphics/drm-next-kmod to Linux 4.11 level for recent CURRENT and 11-STABLE

2018-02-26 Thread Ronald Klop
On Sun, 25 Feb 2018 16:48:44 +0100, Johannes M Dieterich wrote: Dear all, Please CC me as I am not subscribed. On behalf of the FreeBSDDesktop team and thanks to the tireless efforts of Johannes Lundberg and Hans Petter Selasky (hselasky), I am pleased to report that the graphics/drm-next-k

Compilation failure of the kernel for drm-next

2018-02-26 Thread Mylan Connolly
Hello all, I'm not sure if this is the best place to send this, but it looks like the issue tracker in Github is a bit dead. I have been trying to compile it for the past few weeks after downloading the latest code about once a week and it looks like this issue hasn't resolved itself. When I

Re: Compilation failure of the kernel for drm-next

2018-02-26 Thread Pete Wright
On 02/26/2018 17:17, Mylan Connolly wrote: Hello all, I'm not sure if this is the best place to send this, but it looks like the issue tracker in Github is a bit dead. there may not be much traffic on it recently, but people are def still actively working on the repository and will see whe