# Paraview download binary build configuration parameters
**URL:** https://discourse.paraview.org/t/paraview-download-binary-build-configuration-parameters/8219
**Category:** ParaView Support
**Created:** [October 19, 2021, 11:39am UTC](https://discourse.paraview.org/t/paraview-download-binary-build-configuration-parameters/8219 "2021-10-19T11:39:20Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@luigi-calori](https://discourse.paraview.org/u/luigi-calori)
#### Post date: [October 19, 2021, 11:39am UTC](https://discourse.paraview.org/t/paraview-download-binary-build-configuration-parameters/8219/1 "2021-10-19T11:39:20Z")
Hi, I’ m trying to build myself paraview to be used with virtualgl glx, opengl and turbovnc.
I’ m trying to use spack recipe for that.
What currently happen is that within the current stack, I’ ve been able to build and run opengl demo, qt examples and vtk
The stack is also able to support the run of paraview 5.9.1 binary
unfortunately, my spack build of paraview 5.9.1 that use the same qt 5.15.2 fails with
warning: In unknown, line 0
warning: The X11 connection broke: No error (code 0)
XIO: fatal IO error 2 (No such file or directory) on X server “:24”
after 480 requests (444 known processed) with 0 events remaining.
So, any suggestion on where could be the problem would be really appreciated.
Also, would it be useful to find what has been used to produce the correctly runnning paraview binary from the site. I searched around but was not able to find the requirements, environment and config setup used for official paraview binary build.
For example, I see from the About panel that the Paraview binary is using internally provided Qt 5.12.9
is this a requirement?
Thanks in advance for any help
---
### Author:  [@luigi-calori](https://discourse.paraview.org/u/luigi-calori)
#### Post date: [October 20, 2021, 1:54pm UTC](https://discourse.paraview.org/t/paraview-download-binary-build-configuration-parameters/8219/2 "2021-10-20T13:54:31Z")
Likely I found the problem:
As I mentrioned before, I was using spack build X11 stack with only openssl and opengl packages discovered by spack as external packages with /usr as prefix.
looking at what were dynamic link resolution with
ldd $(which paraview) | grep /usr/lib
I found that some x11 libraries were RPATH linked from the system ( /usr/lib64 )
When added to paraview the needed dependencies, the previous libs where correctly taken from spack install and the error gone.
I’ll submit an issue in spack and relative PR