You can choose a different version of OpenGL libraries by setting the LD_LIBRARY_PATH. If it points to where the Mesa libraries are, ParaView should use those first.
By the way, are you seeing any significant performance different between Mesa and Intel drivers? Also, is there any way to enable Intel support when compiling Mesa? I suspect that the Intel drivers are already Mesa based. -berk On Sat, Dec 19, 2009 at 8:58 AM, Andrew Lofthouse <[email protected]> wrote: > I've now narrowed the problem to libGL.so. The libGL.so that ships with F12 > is /usr/lib64/libGL.so.1.2, with /usr/lib64/libGL.so.1 pointing to it. The > version that I compiled from source (using the generic build instructions to > get software rendering) is libGL.so.1.5.070601. If I point > /usr/lib64/libGL.so.1 to my new libGL (libGL.so.1.5.070601), *and run the > version of Paraview that ships with F12* (not my customized build), then the > label problem is not present. > > I don't know if this is due to a newer version of libGL, or if it is because > I compiled that version of libGL without hardware acceleration. Any insight > from others? > > I would like to keep the original version of libGL -- so I'd like Paraview > to look for libGL.so.1.5, instead of libGL.so.1. Perhaps I'll need to > statically link Paraview to libGL? Any suggestions as to how best to keep > the hardware accelerated version of libGL, but point Paraview to the > in-software-only libGL? > _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
