# Failling to build ParaView-Superbuild
**URL:** https://discourse.paraview.org/t/failling-to-build-paraview-superbuild/16268
**Category:** Development
**Created:** [March 7, 2025, 1:15am UTC](https://discourse.paraview.org/t/failling-to-build-paraview-superbuild/16268 "2025-03-07T01:15:56Z")
**Posts on this page:** 14
**Page:** 1
### Author:  [@ar-valdez](https://discourse.paraview.org/u/ar-valdez)
#### Post date: [March 7, 2025, 1:15am UTC](https://discourse.paraview.org/t/failling-to-build-paraview-superbuild/16268/1 "2025-03-07T01:15:56Z")
Hi, I am trying to build `ParaView-Superbuild` from scratch. I want to install two plugins, (i) `superquadrics` to render and visualize sphero cylinders [[MercuryDPM: Visualising Superquadrics in Paraview](http://docs.mercurydpm.org/Trunk/d9/d86/ParaViewSuperbuild.html)], and (ii) I want to enable Virtual Reality using `OpenVR` (note that `OpenXR` lost support last year, 2024).
Before even doing anything of this fancy build, I tried the default build to see how far I can get with my `Ubuntu 24.04.2 LTS`. Well, I generate the `MakeFile` but it fails to build. Let me share the error that pops out.
`CMake Error at /home/ar-valdez/anaconda3/share/cmake-3.28/Modules/FindPackageHandleStandardArgs.cmake:230 (message): Could NOT find X11 (missing: X11_X11_LIB) Call Stack (most recent call first): /home/ar-valdez/anaconda3/share/cmake-3.28/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE) VTK/CMake/patches/99/FindX11.cmake:665 (find_package_handle_standard_args) VTK/ThirdParty/glad/vtkglad/CMakeLists.txt:51 (find_package) -- Configuring incomplete, errors occurred! CMake Error at /home/ar-valdez/paraview-superbuild/build/superbuild/sb-paraview-configure.cmake:48 (message): Failed with exit code 1`
The curious fact is that I DO have installed that `X11` library…
`libx11-dev is already the newest version (2:1.8.7-1build1). libx11-dev set to manually installed.`
Is anyone facing this problem too? All help and comments are welcome…
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [March 7, 2025, 8:03am UTC](https://discourse.paraview.org/t/failling-to-build-paraview-superbuild/16268/2 "2025-03-07T08:03:59Z")
> `anaconda3/share/cmake-3.28`
Can you try configuring `superbuild/paraview/build` with `--debug-find`? I suspect that Anaconda might not be searching the system by default. Possible solutions (in no particular order):
- download a separate CMake and use it (running `.gitlab/ci/cmake.sh` from the top of the repo will drop a suitable one to `.gitlab/cmake/bin/cmake`)
- install X11 libraries in Anaconda
- use an `apt install cmake`
---
### Author:  [@ar-valdez](https://discourse.paraview.org/u/ar-valdez)
#### Post date: [March 7, 2025, 9:44pm UTC](https://discourse.paraview.org/t/failling-to-build-paraview-superbuild/16268/3 "2025-03-07T21:44:58Z")
Same mistake occurs, even deactivating `(base)` doing `conda deactivate`, I can confirm that cmake is installed version 3.28.3
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [March 8, 2025, 9:28pm UTC](https://discourse.paraview.org/t/failling-to-build-paraview-superbuild/16268/4 "2025-03-08T21:28:29Z")
Can you get the relevant X11 output from configuring ParaView with the `--debug-find` flag?
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [March 9, 2025, 10:52am UTC](https://discourse.paraview.org/t/failling-to-build-paraview-superbuild/16268/5 "2025-03-09T10:52:31Z")
> [@ar-valdez](#):
>
> Could NOT find X11 (missing: X11\_X11\_LIB)
it is caused by anaconda: [Could NOT find X11 (missing: X11\_X11\_LIB) · Issue #1957 · glfw/glfw · GitHub](https://github.com/glfw/glfw/issues/1957)
---
### Author:  [@ar-valdez](https://discourse.paraview.org/u/ar-valdez)
#### Post date: [March 10, 2025, 2:00am UTC](https://discourse.paraview.org/t/failling-to-build-paraview-superbuild/16268/6 "2025-03-10T02:00:46Z")
> [@ben.boeckel](#):
>
> –debug-find
Well, what can I say. I “deactivated conda” `conda deactivate` The mistake persists after generating the makefile…and hitting `make -j10`… Sorry this should be for @mwestphal… What can I do, beyond deactivating conda? Thank you.-
---
### Author:  [@ar-valdez](https://discourse.paraview.org/u/ar-valdez)
#### Post date: [March 10, 2025, 2:02am UTC](https://discourse.paraview.org/t/failling-to-build-paraview-superbuild/16268/7 "2025-03-10T02:02:32Z")
Hi Thanks for the response. I did your advice the terminal output is kind long to paste it here. Should I be looking for anything in particular? I can send it by email if you want to check the log…
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [March 10, 2025, 11:36am UTC](https://discourse.paraview.org/t/failling-to-build-paraview-superbuild/16268/8 "2025-03-10T11:36:57Z")
If you can clip it to the X11-searching bits, that should fit here. Or on a pastebin of your choice.
> [@ar-valdez](#):
>
> Well, what can I say. I “deactivated conda” `conda deactivate` The mistake persists after generating the makefile…and hitting `make -j10`… Sorry this should be for @mwestphal… What can I do, beyond deactivating conda? Thank you.-
Generally you need a clean build (nuke `install/` and `superbuild/`), not just a clean configure for a clean superbuild.
---
### Author:  [@ar-valdez](https://discourse.paraview.org/u/ar-valdez)
#### Post date: [March 12, 2025, 4:12am UTC](https://discourse.paraview.org/t/failling-to-build-paraview-superbuild/16268/9 "2025-03-12T04:12:05Z")
Hello, this is my output file. Look at it, I get the same output if I do `conda deactivate`.Thanks Ben.
[out.log](https://discourse.paraview.org/uploads/short-url/koWK4SnqGMjOeUhlUWwxbDR0mH.log) (86.2 KB)
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [March 13, 2025, 9:15am UTC](https://discourse.paraview.org/t/failling-to-build-paraview-superbuild/16268/10 "2025-03-13T09:15:04Z")
That’s the output of the superbuild’s configure. The output of ParaView’s configure with the extra debugging is required (this is where X11 is searched for).
> [@ben.boeckel](#):
>
> Can you try configuring `superbuild/paraview/build` with `--debug-find`?
I suppose you could also stick a `find_package(X11)` in the superbuild’s cmake and configure with it and `--find-debug`…probably a lot less noise there.
---
### Author:  [@ar-valdez](https://discourse.paraview.org/u/ar-valdez)
#### Post date: [March 21, 2025, 2:44pm UTC](https://discourse.paraview.org/t/failling-to-build-paraview-superbuild/16268/11 "2025-03-21T14:44:16Z")
Not sure how to ask cmake to find `X11`. How should the terminal command look like?
`>> ccmake --find-debug find_package(X11) ..`? Thanks.-
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [March 21, 2025, 3:59pm UTC](https://discourse.paraview.org/t/failling-to-build-paraview-superbuild/16268/12 "2025-03-21T15:59:48Z")
Edit the superbuild’s top-level `CMakeLists.txt` to have `find_package(VTK)` and then configure with the `--find-debug` flag.
---
### Author:  [@ar-valdez](https://discourse.paraview.org/u/ar-valdez)
#### Post date: [April 8, 2025, 9:29pm UTC](https://discourse.paraview.org/t/failling-to-build-paraview-superbuild/16268/13 "2025-04-08T21:29:45Z")
Sorry to fail in answering fast. Let me ask you a different question since the log output is very similar to the original log… Do I need to run the superbuild in order to visualize Superquadrics? I noticed that I don’t need the superbuild for VR. Perhaps I don’t need it either for superquadrics… Here @mwestphal solved the task, I guess, but couldn’t find a reference to his answer [[Superquadric attributes exact definition - #2 by mwestphal](https://discourse.paraview.org/t/superquadric-attributes-exact-definition/3205/2)]. I never used Paraview as an import from Python. I can create a new topic question if you think is better.
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [April 8, 2025, 10:41pm UTC](https://discourse.paraview.org/t/failling-to-build-paraview-superbuild/16268/14 "2025-04-08T22:41:52Z")
> [@ar-valdez](#):
>
> I never used Paraview as an import from Python. I can create a new topic question if you think is better.
Yes, please use a new thread for new topics.