On 23 February 2017 at 10:20, Marc Dietrich <marvi...@gmx.de> wrote: > Am Donnerstag, 23. Februar 2017, 10:54:39 CET schrieb Michel Dänzer: >> On 23/02/17 06:39 PM, Marc Dietrich wrote: >> > Am Donnerstag, 23. Februar 2017, 04:10:23 CET schrieb Timothy Arceri: >> >> I've pushed a fix for building with an old version of llvm. Hopefully >> >> this will resolve your problem. >> > >> > I have a pretty current version of llvm (3.9.1), so the problem is not >> > fixed by this patch :-) From the fact that it works for you and others, I >> > guess it must be some distro packaging problem (suse thumbleweed here). >> > llvm is using shared libs. >> >> FWIW, this is broken packaging on SUSE's part — they need to build LLVM >> with LLVM_BUILD_LLVM_DYLIB=ON instead of BUILD_SHARED_LIBS=ON. The >> latter is an unsupported developer only option. Please report this to them. > > does this mean that multiple shared libs are not supported by mesa? I read > from the llvm website, that > > "BUILD_SHARED_LIBS is only recommended for use by LLVM developers. If you want > to build LLVM as a shared library, you should use the LLVM_BUILD_LLVM_DYLIB > option." > > I wonder why mesa tries to gather a list of required libs then (for static > linking maybe?) > Yes, collecting the required libs is for static linking. Care to send a patch which moves it within the correct section - 20-30 lines further down ;-)
>> >> > So the remaining question is what actually pulls in LLVMAMDGPUInfo, and >> > why >> > isn't it pulled here? >> >> This may still need to be answered for linking LLVM statically though. > > Unfortunately, opensuse does not provide static libs.... > > Will also add this to the bug report. > Great, thank you ! Emil _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
