Date: Mon, 25 Dec 2017 12:35:02 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 219562] lang/pocl: crash during initialization Message-ID: <bug-219562-13-S6SncgTiSJ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-219562-13@https.bugs.freebsd.org/bugzilla/> References: <bug-219562-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219562 --- Comment #7 from O. Hartmann <ohartmann@walstatt.org> --- I just try to update our port from pocl 0.14 to pocl 1.0, since pocl-1.0 is= out for a couple of days now. The problem the initial poster faced is still persistent and I was searching the net for some solutions. I'm not a compiler expert and my resources are limited. I tried compiling lang/pocl with the option by setting SINGLE_LLVM_LIB=3DON via cmake, but this put a considerable load and compile time to the port bu= ild I do not want to bear. Searching the bug databse at LLVM.ORG, I found some references to this type= of bug, but at different places and I'm wondering if this is still with FreeBS= D's implementation of CLANG/LLVM. [...] Don't link ObjCARCOpts twice. Fixes PR22543 https://reviews.llvm.org/rL240104 and another one, which seems unresolved to me, is this one: [...] Bug 22952: cl::opt + LLVM_BUILD_LLVM_DYLIB is completely broken https://bugs.llvm.org/show_bug.cgi?id=3D22952 Since I use on most recent CURRENT still the default linker, which is ld.bf= d, I have not checked whether this problem is still with the LLVM/CLANG ld.lld linker, since using the new linker causes a lot of trouble with important ports. It would be great if someone with a more decent insight into this LLVM link= er stuff could take a look. Thanks in advance, oh --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219562-13-S6SncgTiSJ>