# Errors with paraview-mesa in ParaView 5.7.0-RC2 for linux both superbuild built versions and with downloaded binary version
**URL:** https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453
**Category:** Development
**Created:** [August 19, 2019, 3:12pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453 "2019-08-19T15:12:43Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@joeh](https://discourse.paraview.org/u/joeh)
#### Post date: [August 19, 2019, 3:12pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/1 "2019-08-19T15:12:43Z")
Hi,
I am having difficulty with paraview-mesa and the mesa superbuild version for ParaView 5.7.0-RC2, the installed directory for the superbuild version does not match the released binaries for 5.7.0-RC2 for linux.
The superbuild built version is not creating a mesa sub-directory in the installed lib directory.
and when
paraview-mesa paraview --backend llvmpipe
or
paraview-mesa paraview --backend swr
is run it cannot find the mesa version and instead is using the nvidia driver version and reporting the errors
./paraview-mesa paraview --backend llvmpipe
( 0.552s) [paraview]vtkOpenGLRenderWindow.c:761 ERR| vtkXOpenGLRenderWindow (0x4043c10): Unable to find a valid OpenGL 3.2 or later implementation. Please update your video card driver to the latest version. If you are using Mesa please make sure you have version 11.2 or later and make sure your driver in Mesa supports OpenGL 3.2 such as llvmpipe or openswr. If you are on windows and using Microsoft remote desktop note that it only supports OpenGL 3.2 with nvidia quadro cards. You can use other remoting software such as nomachine to avoid this issue.
./paraview-mesa paraview --backend swr
( 0.497s) [paraview]vtkOpenGLRenderWindow.c:761 ERR| vtkXOpenGLRenderWindow (0x31780e0): Unable to find a valid OpenGL 3.2 or later implementation. Please update your video card driver to the latest version. If you are using Mesa please make sure you have version 11.2 or later and make sure your driver in Mesa supports OpenGL 3.2 such as llvmpipe or openswr. If you are on windows and using Microsoft remote desktop note that it only supports OpenGL 3.2 with nvidia quadro cards. You can use other remoting software such as nomachine to avoid this issue.
This is on a RHEL 7.7 system with glxinfo reporting
OpenGL renderer string: Quadro M4000/PCIe/SSE2
OpenGL version string: 3.0.0 NVIDIA 418.43
The downloaded binaries do not have this particular issue and are finding the llvmpipe and swr
mesa backends included with the binaries in the mesa sub-directory.
But even with the downloaded binaries I am still getting the following errors.
with llvmpipe I get the error
Error: Unsupported device
WARNING: Failed to initialize RTW VisRTX backend.
while for swr I get the slightly different error
SWR detected AVX2 instruction support (using: libswrAVX2.so).
Error: Unsupported device
WARNING: Failed to initialize RTW VisRTX backend.
yet the rendering still seems to be working in both cases
Any ideas as to the causes of these issues?
Thanks,
Joe Hennessey
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [August 19, 2019, 8:19pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/2 "2019-08-19T20:19:29Z")
> I am having difficulty with paraview-mesa and the mesa superbuild version for ParaView 5.7.0-RC2, the installed directory for the superbuild version does not match the released binaries for 5.7.0-RC2 for linux.
The `mesa` subdirectory is created by the packaging step (`ctest -R cpack-paraview`). The `install` directory in the superbuild is just a staging place for all the packages to “gather” in before the packaging goes and puts them all in the right place. For Linux, that’s mostly a no-op, but there are details that are happening there (the `mesa` relocation being one of them).
If that is all OK, what is output if you add `--print` to `paraview-mesa`? Is there anything interesting if run under a `LD_DEBUG=libs,files` environment setting?
> Error: Unsupported device
> WARNING: Failed to initialize RTW VisRTX backend.
This seems to be something VisRTX-related (though apparently harmless). @Dave_DeMarle? The AVX2 message is purely informational (it’s saying what CPU features it detected that it can use).
---
### Author:  [@joeh](https://discourse.paraview.org/u/joeh)
#### Post date: [August 19, 2019, 8:30pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/3 "2019-08-19T20:30:50Z")
Ben,
Here is the superbuild version output with the llvmpipe and swr options,
that fails to render properly
./paraview-mesa paraview --backend llvmpipe --print
LD\_LIBRARY\_PATH=/home/joeh/pv-test/5.7.0-RC2\_mesa/bin/…/lib
GALLIUM\_DRIVER=llvmpipe
( 0.548s) [paraview]vtkOpenGLRenderWindow.c:761 ERR| vtkXOpenGLRenderWindow (0x3e3b8c0): Unable to find a valid OpenGL 3.2 or later implementation. Please update your video card driver to the latest version. If you are using Mesa please make sure you have version 11.2 or later and make sure your driver in Mesa supports OpenGL 3.2 such as llvmpipe or openswr. If you are on windows and using Microsoft remote desktop note that it only supports OpenGL 3.2 with nvidia quadro cards. You can use other remoting software such as nomachine to avoid this issue.
/paraview-mesa paraview --backend swr --print
LD\_LIBRARY\_PATH=/home/joeh/pv-test/5.7.0-RC2\_mesa/bin/…/lib
GALLIUM\_DRIVER=swr
( 0.532s) [paraview]vtkOpenGLRenderWindow.c:761 ERR| vtkXOpenGLRenderWindow (0x34e3c20): Unable to find a valid OpenGL 3.2 or later implementation. Please update your video card driver to the latest version. If you are using Mesa please make sure you have version 11.2 or later and make sure your driver in Mesa supports OpenGL 3.2 such as llvmpipe or openswr. If you are on windows and using Microsoft remote desktop note that it only supports OpenGL 3.2 with nvidia quadro cards. You can use other remoting software such as nomachine to avoid this issue.
And, here is the binary from kitware with the llvmpipe and swr options,
this version again works but complains.
./paraview-mesa paraview --backend llvmpipe --print
LD\_LIBRARY\_PATH=/home/joeh/Downloads/paraview\_test/ParaView-5.7.0-RC2-MPI-Linux-Python2.7-64bit/bin/…/lib/mesa
GALLIUM\_DRIVER=llvmpipe
Error: Unsupported device
WARNING: Failed to initialize RTW VisRTX backend.
./paraview-mesa paraview --backend swr --print
LD\_LIBRARY\_PATH=/home/joeh/Downloads/paraview\_test/ParaView-5.7.0-RC2-MPI-Linux-Python2.7-64bit/bin/…/lib/mesa
GALLIUM\_DRIVER=swr
SWR detected AVX2 instruction support (using: libswrAVX2.so).
Error: Unsupported device
WARNING: Failed to initialize RTW VisRTX backend.
Error: Unsupported device
Thanks,
Joe
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [August 20, 2019, 1:28pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/4 "2019-08-20T13:28:16Z")
> [@joeh](#):
>
> LD\_LIBRARY\_PATH=/home/joeh/pv-test/5.7.0-RC2\_mesa/bin/…/lib
This tells me that your superbuild was built without `mesa`. Looking at the logic, it looks like `PARAVIEW_DEFAULT_SYSTEM_GL=ON` is passed to our libraries (which makes them default to the system GL, but ship Mesa in another directory). With that `OFF` (the default when `mesa` is built), we just add the libGL to the directory and use it via `RPATH` settings. Does it work when not using `paraview-mesa` in that case? Is it using Mesa then?
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [August 20, 2019, 1:28pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/5 "2019-08-20T13:28:55Z")
@chuckatkins
---
### Author:  [@joeh](https://discourse.paraview.org/u/joeh)
#### Post date: [August 20, 2019, 4:02pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/6 "2019-08-20T16:02:33Z")
Ben,
The superbuild built Mesa, and mesa is in the lib directory of ParaView, but not in a mesa subdirectory
like the ParaView binaries have mesa in.
It does not work when ParaView is called directly and ParaView does not seem to call mesa.
It produces the same error and tries to use the nvidia version of GL
instead of the mesa version and then fails as the nvidia version on this system
only supports OpenGL 3.0.0 when it needs a minimum of OpenGL 3.2.0
to function.
Thanks,
Joe
---
### Author:  [@joeh](https://discourse.paraview.org/u/joeh)
#### Post date: [August 26, 2019, 2:20pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/7 "2019-08-26T14:20:48Z")
Ben,
I ran paraview with LD\_DEBUG=libs,files and got this output,
I have inserted the interersting sections, it seems to start using the wrong libraries
starting here where libGLX is loading the nvidia driver instead of the internal mesa libraries.
```
15973: file=libGLX_nvidia.so.0 [0]; dynamically loaded by /lib64/libGLX.so.0 [0]
15973: find library=libGLX_nvidia.so.0 [0]; searching
15973: search path=/home/joeh/pv-test/5.7.0-RC2_mesa/bin/../lib:/home/joeh/PV/Build_5.7.0-RC2_mesa/install/lib:/home/joeh/PV/Build_5.7.0-RC2_mesa/install/lib64 (RPATH from file /home/joeh/pv-test/5.7.0-RC2_mesa/bin/paraview)
15973: trying file=/home/joeh/pv-test/5.7.0-RC2_mesa/bin/../lib/libGLX_nvidia.so.0
15973: trying file=/home/joeh/PV/Build_5.7.0-RC2_mesa/install/lib/libGLX_nvidia.so.0
15973: trying file=/home/joeh/PV/Build_5.7.0-RC2_mesa/install/lib64/libGLX_nvidia.so.0
15973: search path=/home/joeh/pv-test/5.7.0-RC2_mesa/bin/../lib (RPATH from file /home/joeh/pv-test/5.7.0-RC2_mesa/bin/paraview)
15973: trying file=/home/joeh/pv-test/5.7.0-RC2_mesa/bin/../lib/libGLX_nvidia.so.0
15973: search cache=/etc/ld.so.cache
15973: trying file=/lib64/libGLX_nvidia.so.0
15973:
15973: file=libGLX_nvidia.so.0 [0]; generating link map
15973: dynamic: 0x00007fe7b7ca1fa0 base: 0x00007fe7b7990000 size: 0x00000000003188a8
15973: entry: 0x00007fe7b79dcab0 phdr: 0x00007fe7b7990040 phnum: 4
15973:
15973:
15973: file=libnvidia-tls.so.430.40 [0]; needed by /lib64/libGLX_nvidia.so.0 [0]
15973: find library=libnvidia-tls.so.430.40 [0]; searching
15973: search path=/home/joeh/pv-test/5.7.0-RC2_mesa/bin/../lib:/home/joeh/PV/Build_5.7.0-RC2_mesa/install/lib:/home/joeh/PV/Build_5.7.0-RC2_mesa/install/lib64 (RPATH from file /home/joeh/pv-test/5.7.0-RC2_mesa/bin/paraview)
15973: trying file=/home/joeh/pv-test/5.7.0-RC2_mesa/bin/../lib/libnvidia-tls.so.430.40
15973: trying file=/home/joeh/PV/Build_5.7.0-RC2_mesa/install/lib/libnvidia-tls.so.430.40
15973: trying file=/home/joeh/PV/Build_5.7.0-RC2_mesa/install/lib64/libnvidia-tls.so.430.40
15973: search path=/home/joeh/pv-test/5.7.0-RC2_mesa/bin/../lib (RPATH from file /home/joeh/pv-test/5.7.0-RC2_mesa/bin/paraview)
15973: trying file=/home/joeh/pv-test/5.7.0-RC2_mesa/bin/../lib/libnvidia-tls.so.430.40
15973: search cache=/etc/ld.so.cache
15973: trying file=/lib64/libnvidia-tls.so.430.40
15973:
15973: file=libnvidia-tls.so.430.40 [0]; generating link map
15973: dynamic: 0x00007fe7b798f0a0 base: 0x00007fe7b778c000 size: 0x0000000000203520
15973: entry: 0x00007fe7b778c9a0 phdr: 0x00007fe7b778c040 phnum: 6
15973:
15973:
15973: file=libnvidia-glcore.so.430.40 [0]; needed by /lib64/libGLX_nvidia.so.0 [0]
15973: find library=libnvidia-glcore.so.430.40 [0]; searching
15973: search path=/home/joeh/pv-test/5.7.0-RC2_mesa/bin/../lib:/home/joeh/PV/Build_5.7.0-RC2_mesa/install/lib:/home/joeh/PV/Build_5.7.0-RC2_mesa/install/lib64 (RPATH from file /home/joeh/pv-test/5.7.0-RC2_mesa/bin/paraview)
15973: trying file=/home/joeh/pv-test/5.7.0-RC2_mesa/bin/../lib/libnvidia-glcore.so.430.40
15973: trying file=/home/joeh/PV/Build_5.7.0-RC2_mesa/install/lib/libnvidia-glcore.so.430.40
15973: trying file=/home/joeh/PV/Build_5.7.0-RC2_mesa/install/lib64/libnvidia-glcore.so.430.40
15973: search path=/home/joeh/pv-test/5.7.0-RC2_mesa/bin/../lib (RPATH from file /home/joeh/pv-test/5.7.0-RC2_mesa/bin/paraview)
15973: trying file=/home/joeh/pv-test/5.7.0-RC2_mesa/bin/../lib/libnvidia-glcore.so.430.40
15973: search cache=/etc/ld.so.cache
15973: trying file=/lib64/libnvidia-glcore.so.430.40
15973:
15973: file=libnvidia-glcore.so.430.40 [0]; generating link map
15973: dynamic: 0x00007fe7b716a2f0 base: 0x00007fe7b5523000 size: 0x0000000001cd48e0
15973: entry: 0x00007fe7b579c0e0 phdr: 0x00007fe7b5523040 phnum: 6
15973:
15973:
15973: calling init: /lib64/libnvidia-glcore.so.430.40
15973:
15973:
15973: calling init: /lib64/libGLX_nvidia.so.0
15973:
15973: opening file=/lib64/libc.so.6 [0]; direct_opencount=1
15973:
15973:
15973: closing file=/lib64/libc.so.6; direct_opencount=0
15973: /lib64/libnvidia-glcore.so.430.40: error: symbol lookup error: undefined symbol: ErrorF (fatal)
15973: opening file= [0]; direct_opencount=2
15973:
15973:
15973: closing file=; direct_opencount=1
15973: opening file= [0]; direct_opencount=2
15973:
15973:
15973: closing file=; direct_opencount=1
15973: opening file=/lib64/libpthread.so.0 [0]; direct_opencount=1
15973:
15973: /lib64/libpthread.so.0: error: symbol lookup error: undefined symbol: pthread_setname_np, version GLIBC_2.2.5 (fatal)
15973: opening file= [0]; direct_opencount=2
15973:
15973:
15973: closing file=; direct_opencount=1
15973: opening file= [0]; direct_opencount=2
15973:
15973:
15973: closing file=; direct_opencount=1
15973: opening file=/lib64/libGLX_nvidia.so.0 [0]; direct_opencount=1
15973:
15973: opening file= [0]; direct_opencount=2
15973:
15973:
15973: closing file=; direct_opencount=1
15973: opening file= [0]; direct_opencount=2
15973:
15973:
15973: closing file=; direct_opencount=1
```
Resulting in this error
( 0.533s) [paraview]vtkOpenGLRenderWindow.c:761 ERR| vtkXOpenGLRenderWindow (0x46aad90): Unable to find a valid OpenGL 3.2 or later implementation. Please update your video card driver to the latest version. If you are using Mesa please make sure you have version 11.2 or later and make sure your driver in Mesa supports OpenGL 3.2 such as llvmpipe or openswr. If you are on windows and using Microsoft remote desktop note that it only supports OpenGL 3.2 with nvidia quadro cards. You can use other remoting software such as nomachine to avoid this issue.
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [August 29, 2019, 12:55pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/8 "2019-08-29T12:55:26Z")
I’m not sure what is looking for that \_nvidia library. That seems like the root cause. @chuckatkins Thoughts? We certainly don’t build that, but we might end up linking against it during the build. Is something not finding the right OpenGL setup from the superbuild?
---
### Author:  [@joeh](https://discourse.paraview.org/u/joeh)
#### Post date: [September 9, 2019, 4:57pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/9 "2019-09-09T16:57:05Z")
I have just built and tested ParaView 5.7.0-RC3 and the same issue still exists.
---
### Author:  [@joeh](https://discourse.paraview.org/u/joeh)
#### Post date: [September 17, 2019, 3:30pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/10 "2019-09-17T15:30:21Z")
I have just built and tested ParaView 5.7.0-RC4 and the same issue still exists.
---
### Author:  [@Andy\_Bauer](https://discourse.paraview.org/u/Andy_Bauer)
#### Post date: [September 18, 2019, 3:55pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/11 "2019-09-18T15:55:32Z")
Is there any information that we can provide to help track down this issue? I believe @cory.quammen has access to the DOD machines that @joeh is trying to build on too if that helps.
---
### Author:  [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)
#### Post date: [September 19, 2019, 12:56pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/12 "2019-09-19T12:56:37Z")
@joeh, since I am joining this conversation anew, I want to clarify a few things:
1. Are [paraView.org](http://paraView.org) binaries working as expected, even with mesa? The errors you originally reported ( `Error: Unsupported device, WARNING: Failed to initialize RTW VisRTX backend.`) should have been fixed in RC4. Also they are safe to ignore, they were really internally debug messages warning about OptiX backend being unavailable.
2. can you attach/email your CMakeCache.txt for the ParaView-Superbuild?
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [September 19, 2019, 1:57pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/13 "2019-09-19T13:57:11Z")
> [@ben.boeckel](#):
>
> I’m not sure what is looking for that \_nvidia library.
My guess is GLVND. See the GLX dispatching section at [GitHub - NVIDIA/libglvnd: The GL Vendor-Neutral Dispatch library](https://github.com/NVIDIA/libglvnd).
@joeh is GLVND installed on that system? If so, then that isn’t necessarily indicative of a linking issue in the build.
---
### Author:  [@joeh](https://discourse.paraview.org/u/joeh)
#### Post date: [September 19, 2019, 1:57pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/14 "2019-09-19T13:57:58Z")
The seem to be two basic problems still.
1. The superbuild will not create a mesa subdirectory in lib to match your binary distribution.
2. While your binary distribution will correctly use mesa when run by
./paraview-mesa paraview --backend llvmpipe --print
the OpenGL Render in the about box shows
llvmpipe (LLVM 7.0, 256 bits)
as it should.
the superbuild version when run with the same parameters,
./paraview-mesa paraview --backend llvmpipe --print
does not use llvmpipe as it should and is instead attempting to use the non-existant nvidia drivers
and reports these errors below. It is not finding the Mesa version of OpenGL.
```auto
( 1.854s) [paraview]vtkOpenGLRenderWindow.c:761 ERR| vtkXOpenGLRenderWindow (0x1162f30): Unable to find a valid OpenGL 3.2 or later implementation. Please update your video card driver to the latest version. If you are using Mesa please make sure you have version 11.2 or later and make sure your driver in Mesa supports OpenGL 3.2 such as llvmpipe or openswr. If you are on windows and using Microsoft remote desktop note that it only supports OpenGL 3.2 with nvidia quadro cards. You can use other remoting software such as nomachine to avoid this issue.
( 3.881s) [paraview]vtkOpenGLRenderWindow.c:761 ERR| vtkXOpenGLRenderWindow (0x3c50c30): Unable to find a valid OpenGL 3.2 or later implementation. Please update your video card driver to the latest version. If you are using Mesa please make sure you have version 11.2 or later and make sure your driver in Mesa supports OpenGL 3.2 such as llvmpipe or openswr. If you are on windows and using Microsoft remote desktop note that it only supports OpenGL 3.2 with nvidia quadro cards. You can use other remoting software such as nomachine to avoid this issue.
```
---
### Author:  [@joeh](https://discourse.paraview.org/u/joeh)
#### Post date: [September 19, 2019, 2:59pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/15 "2019-09-19T14:59:49Z")
Cory,
Should GLVND be being built as part of the superbuild process?
Theses nodes (login nodes) do not have GPU’s so they do not have
the nvidia drivers installed which is why I need to use Mesa.
Thanks,
Joe
---
### Author:  [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)
#### Post date: [September 19, 2019, 3:48pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/16 "2019-09-19T15:48:45Z")
@joeh, okay, seems like there’s just 1 problem… **the superbuild does not put mesa libs under sub directory**. The second issue is simply a side effect of 1. Can you email me your CMakeCache.txt please?
More specifically, what is the value for `PARAVIEW_DEFAULT_SYSTEM_GL`? As @ben.boeckel mentioned in an earlier post, that needs to be set to `TRUE` for the mesa-sub dirs to be created.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [September 19, 2019, 3:49pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/17 "2019-09-19T15:49:03Z")
> [@joeh](#):
>
> Should GLVND be being built as part of the superbuild process
No, GLVND is a library that would be installed on the system independently from building ParaView or installation. If the node on which you are running doesn’t have NVIDIA drivers, I don’t know why libGLX is trying to load those drivers.
---
### Author:  [@joeh](https://discourse.paraview.org/u/joeh)
#### Post date: [September 19, 2019, 4:02pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/18 "2019-09-19T16:02:19Z")
CLASSIFICATION: UNCLASSIFIED
Utkarsh,
Here are both my paraview superbuild cache, and
the paraview superbuild’s internal paraview cache as well.
Thanks,
Joe
[CMakeCache\_superbuild.txt](https://discourse.paraview.org/uploads/short-url/iDX0KGuIdAx6X9i0wEwgq6VCgja.txt) (50.3 KB)
[CMakeCache\_paraview.txt](https://discourse.paraview.org/uploads/short-url/aa2yTdjhSQF53yeUZAWDkcffBBh.txt) (321 KB)
---
### Author:  [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)
#### Post date: [September 19, 2019, 4:09pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/19 "2019-09-19T16:09:10Z")
looks like **PARAVIEW\_DEFAULT\_SYSTEM\_GL** is indeed **OFF**. Mind setting it to **ON**? That should address the missing mesa-subdir issue. That will also ensure that when you run `./paraview-mesa paraview --backend llvmpipe`, it will load the mesa libs from the sub-directory.
**PARAVIEW\_DEFAULT\_SYSTEM\_GL=OFF** should in theory be expected to work too. But looks like there’s some bug with that and can be tracked down independently later on (when @ben.boeckel is back online).
---
### Author:  [@joeh](https://discourse.paraview.org/u/joeh)
#### Post date: [September 19, 2019, 6:05pm UTC](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453/20 "2019-09-19T18:05:01Z")
Utkarsh,
I tried setting that variable in my curent build and it did create the mesa subdirectory under lib and put the libraries there, it still did not use them though. I am trying again now, with a clean build to see if that helps. This will take a while to finish compilation. I will let you know once it is done. (probably tomorrow)
Thanks,
Joe
[Next page](https://discourse.paraview.org/t/errors-with-paraview-mesa-in-paraview-5-7-0-rc2-for-linux-both-superbuild-built-versions-and-with-downloaded-binary-version/2453.md?page=2)