Dylan Baker <dy...@pnwbakers.com> writes: > Quoting Francisco Jerez (2017-12-13 13:01:29) >> Jan Vesely <jan.ves...@rutgers.edu> writes: >> > meson asked for libdrm_amdgpu dependency even though I'm only building >> > clover+r600g driver. >> > after a bit of fiddling with PATH and PK_CONFIG_PATH to pick up the latest >> > llvm/liblclc >> > linking failed with: >> > src/gallium/auxiliary/libgallium.a(gallivm_lp_bld_misc.cpp.o):(.data.rel.ro._ZTI26DelegatingJITMemoryManager[_ZTI26DelegatingJITMemoryManager]+0x10): >> > undefined reference to `typeinfo for llvm::RTDyldMemoryManager' >> > collect2: error: ld returned 1 exit status >> > >> > this looks like it did not pick up the rtti setting from llvm-config: >> > $ ~/.local/bin/llvm-config --has-rtti >> > NO >> > $ ~/.local/bin/llvm-config --cxxflags | grep -o fno-rtti >> > fno-rtti >> > >> > rtti setting is quite messy since clover uses dynamic_cast. I think it >> > should be OK to only support rtti build of llvm if it's detected at >> > configure time >> >> Is that any different with autotools? Clover is not meant to link >> against an -fno-rtti LLVM, because an LLVM library built in such a way >> has a non-standard C++ ABI. Picking up the -fno-rtti flag from >> llvm-config is not guaranteed to fix anything. Attempting to do so >> should probably lead to a build error at configure time... > > I can add some logic to detect `-fno-rtti` and error out if you think that's > the > right thing to do.
That would be great, but I wouldn't set it as a requirement for the meson build, since the autotools build system is lacking the same feature ;)
signature.asc
Description: PGP signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
