Bugzilla – Bug 59282
Undefined symbol '_ZTVN10__cxxabiv120__si_class_type_infoE' in r600_dri.so
Last modified: 2013-01-13 11:29:12 UTC
Mesa from git master (head 3c3a2b51b85a90cfe670e1ca81ce86c8fa0d448d) has a undefined symbol in r600_dri.so, which prevents it from being loaded:
$ LIBGL_DEBUG=verbose glxinfo
libGL: OpenDriver: trying /usr/lib64/dri/r600_dri.so
libGL error: dlopen /usr/lib64/dri/r600_dri.so failed (/usr/lib64/dri/r600_dri.so: undefined symbol: _ZTVN10__cxxabiv120__si_class_type_infoE)
libGL error: unable to load driver: r600_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: r600
--with-dri-drivers= --with-gallium-drivers=swrast,r600 --enable-gallium-llvm --enable-gallium-egl --with-egl-platforms=x11,drm --enable-gles1 --enable-gles2 --enable-glx-tls --enable-texture-float --enable-shared-glapi
I tried adding radeonsi to the list and see if this fixes it, but in order to build this I have to install LLVM 3.2, which I'm not planning to do today.
This is the commit where this problems starts:
Perhaps this bug is related: https://bugs.freedesktop.org/show_bug.cgi?id=59226
Created attachment 72916 [details] [review]
targets/dri-r600: Force c++ linker in all cases
Could you test this patch?
I made a patch myself, and it works:
--- src/gallium/targets/dri-r600/Makefile.am.orig 2013-01-12 20:00:04.000000000 +0100
+++ src/gallium/targets/dri-r600/Makefile.am 2013-01-12 21:18:15.494000000 +0100
@@ -59,17 +59,13 @@
r600_dri_la_LINK = $(CXXLINK) $(r600_dri_la_LDFLAGS)
# Mention a dummy pure C++ file to trigger generation of the $(LINK) variable
nodist_EXTRA_r600_dri_la_SOURCES = dummy-cpp.cpp
r600_dri_la_LDFLAGS += $(LLVM_LDFLAGS)
r600_dri_la_LIBADD += $(LLVM_LIBS)
-r600_dri_la_LINK = $(LINK) $(r600_dri_la_LDFLAGS)
-# Mention a dummy pure C file to trigger generation of the $(LINK) variable
-nodist_EXTRA_r600_dri_la_SOURCES = dummy-c.c
# Provide compatibility with scripts for the old Mesa build system for
I'm gonna try your patch now.
Andreas, it works, eveyrthing is fine. Thanks.
*** Bug 59296 has been marked as a duplicate of this bug. ***
Yes the patch fixes the problem.
I assume you're going to commit this soon and close this bug report.
Let's keep this bug open until the fix is actually committed.
Fixed by 9da454f295062500ebb868e31eebcd5f753f83ff