<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - SWR doesn't work with OSMesa" href="https://bugs.freedesktop.org/show_bug.cgi?id=110716#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - SWR doesn't work with OSMesa" href="https://bugs.freedesktop.org/show_bug.cgi?id=110716">bug 110716</a> from <a class="email" href="mailto:krzysztof.raszkowski@intel.com" title="Krzysztof Raszkowski <krzysztof.raszkowski@intel.com>"> Krzysztof Raszkowski</a> <pre>Chuck, I've noticed that libOSMesa is distributed in two places (I use ParaView-5.6.0-osmesa-MPI-Linux-64bit.tar.gz): - ParaView-5.6.0-osmesa-MPI-Linux-64bit/lib/libOSMesa.so - ParaView-5.6.0-osmesa-MPI-Linux-64bit/lib/mesa/libOSMesa.so What I see after adding to LD_LIBRARY_PATH my mesa build libraries Paraview always load this "ParaView-5.6.0-osmesa-MPI-Linux-64bit/lib/libOSMesa.so" instead of what I've build (without removing it I've also had some weird errors). Could you verify that this test load libraries you think it should load? You can do it using strace command: strace bin/pvpython /root/ParaView-5.6.0-osmesa-MPI-Linux-64bit/lib/python2.7/site-packages/paraview/benchmark/manyspheres.py &> strace.out Then cat strace.out | grep open | grep libOSMesa and cat strace.out | grep open | grep libswr Thanks, Krzysztof</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>