[Paraview] Software Rendering

John Biddiscombe biddisco at cscs.ch
Tue Jan 23 03:24:00 EST 2007

> OPENGL_INCLUDE_DIR                   /usr/include
> OPENGL_gl_LIBRARY                       /usr/X11R6/lib64/libGL.so
> OPENGL_glu_LIBRARY                     /usr/X11R6/lib64/libGLU.so 
> OSMESA_INCLUDE_DIR                  /usr/include
> OSMESA_LIBRARY                           /usr/X11R6/lib64/libOSMesa.so

Try this : point these to your Mesa build. Mine looks like this...

 OPENGL_INCLUDE_DIR               /home/biddisco/Mesa-6.5.1/include
 OPENGL_gl_LIBRARY                /home/biddisco/Mesa-6.5.1/lib/libGL.so
 OPENGL_glu_LIBRARY               /home/biddisco/Mesa-6.5.1/lib/libGLU.so
 OPENGL_xmesa_INCLUDE_DIR         /home/biddisco/Mesa-6.5.1/include
 OSMESA_INCLUDE_DIR               /home/biddisco/Mesa-6.5.1/include
 OSMESA_LIBRARY                   /home/biddisco/Mesa-6.5.1/lib/libOSMesa.so

So that the GL is Mesa GL and not the system GL. This ought to help 
prevent the app picking up the wrong one.



> I thought I wanted to use the off-screen rendering OSMesa library and 
> not mangled mesa.  Most of these settings were detected and set by 
> cmake.  Everything builds OK, but when I try to run paraview itself, 
> pvclient, or one of the servers, here is what I get:
> /export/linux/lib/paraview-2.4/pvclient-real: relocation error: 
> /usr/X11R6/lib64/libOSMesa.so.4: undefined symbol: _glapi_Dispatch
> Neither my libGL or libOSMesa libraries have symbol tables so I am not 
> able to verify the existence of _glapi_Dispatch, but there are 
> references of sorts in both (using strings command).
> Where have I gone awry?
> Thanks in advance for any and all help.
> Jim

John Biddiscombe,                            email:biddisco @ cscs.ch
CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
Via Cantonale, 6928 Manno, Switzerland      | Fax:  +41 (91) 610.82.82

More information about the ParaView mailing list