On 08/06/2010 03:15 PM, tom fogal wrote: > > If you could build VTK with just a single GL library -- i.e. with just > libOSMesa or just libGL, but not both -- and could reproduce the crash, > that would rule out my symbol collision theory. I am not sure how easy > that is, though... >
That was shockingly easy... sort of. I did my VTK build with both -DOPENGL_gl_LIBRARY:FILEPATH=/tmp/mesa/lib64/libOSMesa.so -DOSMESA_LIBRARY:FILEPATH=/tmp/mesa/lib64/libOSMesa.so and I left off -fvisibility=hidden thinking that I want the symbols that are now included in libOSMesa.so to be available to VTK. and what do you know the test passed. however I wanted to see if VTK is really built with only libOSMesa.so so I did : $ ldd ../VTK_Build/bin/RenderingCxxTests | grep mesa libOSMesa.so.7 => /tmp/mesa/lib64/libOSMesa.so.7 (0x00007fa97ff4a000) libGL.so.1 => /tmp/mesa/lib64/libGL.so.1 (0x00007fa97bc7a000) so it got pulled in somehow perhaps by libOSMesa.so itself? If I do : $ ldd ../mesa/lib64/libOSMesa.so | grep libGL.so libGL.so.1 => /usr/lib64/nvidia/libGL.so.1 (0x00007f88ed2cf000) because libOSMesa.so needs libGL.so and I have the nvidia drivers in my dynamic linker path but VTK has an rpath set so... What does all of this mean?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
