Date: Wed, 28 Aug 2019 07:46:15 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 239682] Default to devel/llvm90 when libLLVM/libclang are required or if /usr/bin/clang is not enough Message-ID: <bug-239682-21738-cwDkSjzxei@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-239682-21738@https.bugs.freebsd.org/bugzilla/> References: <bug-239682-21738@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=3D239682 --- Comment #18 from Jan Beich <jbeich@FreeBSD.org> --- (In reply to Mark Linimon from comment #17) Runtime. Loading more than one libLLVM.so version can lead to crashes. A consumer cannot block other consumers from switching. If only one devel/llvm existed (like in OpenBSD Ports) then it'd be mainly about making consumers build. For example, OpenGL application can load LLVM via graphics/mesa-dri and as = part of its own usage. In the past emulators/rpcs3 was affected until it switche= d to static linking and later to bundled LLVM copy of development snapshot. Currently, I suspect lang/clover is affected. Pining mesa-dri and blocking OpenGL-based LLVM consumers from switching just because a barely usable Ope= nCL implementation isn't compatible yet due to being based on very old upstream release would be silly. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-239682-21738-cwDkSjzxei>