On 5 October 2017 at 17:28, Jan Vesely <jan.ves...@rutgers.edu> wrote: > On Thu, 2017-10-05 at 11:19 +0100, Emil Velikov wrote: >> From: Emil Velikov <emil.veli...@collabora.com> >> >> Otherwise we error out at link stage as follows: >> >> /usr/lib/llvm-3.9/lib/libLLVMAMDGPUCodeGen.a(R600OptimizeVectorRegisters.cpp.o): >> unrecognized relocation (0x2a) in section >> `.text._ZNK12_GLOBAL__N_119R600VectorRegMerger16getAnalysisUsageERN4llvm13AnalysisUsageE' >> /usr/bin/ld: final link failed: Bad value >> >> Cc: mesa-sta...@lists.freedesktop.org >> Cc: Jan Vesely <jan.ves...@rutgers.edu >> Signed-off-by: Emil Velikov <emil.veli...@collabora.com> >> --- >> Suspecting that there are due to LLVM/Clang itself being built with the >> newer version. Something like that seems to be mentioned below. >> AKA packaging bug or we're using the wrong package ;-) >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808205 >> >> AFAICT it has nothing to do with linking against libclang.so > > it does, in a way that linking to dynamic library does not hit this > issue. > Right, that's how to bypass. I'm thinking about the root cause ;-)
>> >> Jan any reason you opted to address only one of the LLVM 3.9 builds? >> Should we bother with the rest, set it globally, other? > > the other builds did not need it. I only hit it when linking to static > clang libraries (for whatever reason it decided to use static > libraries). I assume you started hitting this when you switched > enable_llvm_shared_libs off by default? > Yes, anything LLVM (project) related that is static linked exhibits the problem. Issue is restricted to 3.9, so I seriously suspect something fishy in the code or package. -Emil _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
