Created attachment 504464 [details, diff] llvm 5 compatibility patch Build failure: /var/tmp/portage/media-libs/mesa-17.1.10/work/mesa-17.1.10/src/gallium/auxiliary/gallivm/lp_bld_misc.cpp: In member function ‘virtual void DelegatingJITMemoryManager::deregisterEHFrames(uint8_t*, uint64_t, size_t)’: /var/tmp/portage/media-libs/mesa-17.1.10/work/mesa-17.1.10/src/gallium/auxiliary/gallivm/lp_bld_misc.cpp:346:56: error: no matching function for call to ‘llvm::RTDyldMemoryManager::deregisterEHFrames(uint8_t*&, uint64_t&, size_t&)’ mgr()->deregisterEHFrames(Addr, LoadAddr, Size); The attached patch fixes the issue.
Patch worked for me but I also had to turn off opencl USE flag.
By upstream policy, 17.1 does not support LLVM 5. The patch you attached was committed upstream as commit 0c67aa84568d4676017d0d309e5ba8832d3b9e1e and is in the 17.2 branch. Please use 17.2 if you want to use LLVM 5.
While I can understand the decision, shouldn't the llvm dependency entry reflect this then - e.g. <sys-devel/llvm-5 for the mesa ebuilds below 17.2?!
(In reply to Carlo from comment #3) > While I can understand the decision, shouldn't the llvm dependency entry > reflect this then - e.g. <sys-devel/llvm-5 for the mesa ebuilds below 17.2?! That's admittedly always been a sore spot in our Mesa packaging, so the dependencies were reworked to handle this kind of case in 17.2 and newer. It was also necessary for slotting LLVM, which I personally hope will help with a lot of the LLVM dependency confusion. Anyway, it was a big enough change that I don't think we wanted to try to do it in the 17.1 ebuilds since they were going to go stable soon (bug 629244). I know that answer doesn't help with 17.1, but hopefully it is solved for good in 17.2.
(In reply to Matt Turner from comment #4) > That's admittedly always been a sore spot in our Mesa packaging, so the > dependencies were reworked to handle this kind of case in 17.2 and newer. Obviously I didn't notice that. Thanks for your reply, Matt.
If there is a known issue why don't we explicit use the llvm at slot 4?
*** Bug 640222 has been marked as a duplicate of this bug. ***
