[vtkusers] OSMESA causes some segfaults

[David Doria]

Wow, what a response, thanks! haha

My answers are inline below:

>  What operating system are you using?
Fedora 11

>  Where does your GL library come from, a package or did you build it
> with Mesa?
The package that ships with F11.

>  Where does your OSMesa library come from, a package or did you build
> it with Mesa?
The package that ships with F11.

>  Are you sure you are linking against the correct GL library?
No.

>  What does 'grep OSMESA_LIBRARY CMakeCache.txt' in your VTK build
> directory say?

[doriad at davedesktop VTK]$ grep OSMESA_LIBRARY CMakeCache.txt
MANGLED_OSMESA_LIBRARY:FILEPATH=/usr/lib/libOSMesa.so
OSMESA_LIBRARY:FILEPATH=/usr/lib/libOSMesa.so
//ADVANCED property for variable: MANGLED_OSMESA_LIBRARY
MANGLED_OSMESA_LIBRARY-ADVANCED:INTERNAL=1
//ADVANCED property for variable: OSMESA_LIBRARY
OSMESA_LIBRARY-ADVANCED:INTERNAL=1


>  What does 'grep OPENGL_gl_LIBRARY CMakeCache.txt' in your VTK build
> directory say?

[doriad at davedesktop VTK]$ grep OPENGL_gl_LIBRARY CMakeCache.txt
OPENGL_gl_LIBRARY:FILEPATH=/usr/lib/libGL.so
//ADVANCED property for variable: OPENGL_gl_LIBRARY
OPENGL_gl_LIBRARY-ADVANCED:INTERNAL=1

>  What does 'ldd DisplayCube | grep GL' say?

[doriad at davedesktop Cube]$ ldd DisplayCube | grep GL
	libGL.so.1 => /usr/lib/nvidia/libGL.so.1 (0x043be000)
	libGLcore.so.1 => /usr/lib/nvidia/libGLcore.so.1 (0x01b61000)

>  What does 'ldd DisplayCube | grep OSMesa' say?

[doriad at davedesktop Cube]$ ldd DisplayCube | grep OSMesa
	libOSMesa.so.6 => /usr/lib/libOSMesa.so.6 (0x00ed1000)

>  Did you build VTK with rpath set?

I don't know what you mean?

>  Does your LD_LIBRARY_PATH shell variable direct the linker to find the
> right GL and OSMesa libraries?

As far as I know I only have one version of each (the built in packages).

As you may be able to tell, I have not done anything (intentionally)
non-standard, so I was expecting it to "just work". If you see
anything glaringly wrong in my responses I'll try to check it out
further. Else maybe I'll just wait till the next Fedora release and
see if it gets fixed.

Thanks again for your help so far,

David