# Problem with Paraview Gitlab Master Build on Linux

**URL:** https://discourse.paraview.org/t/problem-with-paraview-gitlab-master-build-on-linux/4996
**Category:** Development
**Created:** [July 31, 2020, 2:51am UTC](https://discourse.paraview.org/t/problem-with-paraview-gitlab-master-build-on-linux/4996 "2020-07-31T02:51:25Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![joeh](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/j/ce7236/32.png) [@joeh](https://discourse.paraview.org/u/joeh)
#### Post date: [July 31, 2020, 2:51am UTC](https://discourse.paraview.org/t/problem-with-paraview-gitlab-master-build-on-linux/4996/1 "2020-07-31T02:51:25Z")

</div>

Hello,

I have found that when building the Paraview Gitlab Master Build on Linux, that  
three symbolic links are missing from the Superbuild/install bin directory

ln -s python3 python  
ln -s python3-config python-config  
ln -s pydoc3 pydoc

The install of the osmesa version (and probably other versions) fails when it can’t find python or python-config (I am not sure if it fails on missing pydoc, but I wanted to be complete).

The install completes if these three symbolic links are made and the superbuild script is attempted to be made again.

Thanks,

Joe Hennessey

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [July 31, 2020, 2:34pm UTC](https://discourse.paraview.org/t/problem-with-paraview-gitlab-master-build-on-linux/4996/2 "2020-07-31T14:34:37Z")

</div>

Thanks, Joe. Thoughts @ben.boeckel @utkarsh.ayachit ?

---

<div class="post-metadata">

### Author: ![utkarsh.ayachit](https://discourse.paraview.org/user_avatar/discourse.paraview.org/utkarsh.ayachit/32/39_2.png) [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)
#### Post date: [July 31, 2020, 2:41pm UTC](https://discourse.paraview.org/t/problem-with-paraview-gitlab-master-build-on-linux/4996/3 "2020-07-31T14:41:05Z")

</div>

@joeh, is the failure building Mesa alone? Seems to me we need to fix mesa build (either pass it different params or patch it) so that it can use the python3 built by the SB. It’s worth figuring out how mesa finds Python and how we can tell it to use a different one.

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [August 7, 2020, 5:06pm UTC](https://discourse.paraview.org/t/problem-with-paraview-gitlab-master-build-on-linux/4996/4 "2020-08-07T17:06:16Z")

</div>

If Mesa can’t deal with a `python` executable missing, it needs to be fixed. It’s a valid configuration that numerous distributions are using. I tend not to have `/usr/bin/python` on my machines because it’s just asking for ambiguities as to what version it actually is (thanks Arch).

---

<div class="post-metadata">

### Author: ![joeh](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/j/ce7236/32.png) [@joeh](https://discourse.paraview.org/u/joeh)
#### Post date: [August 13, 2020, 4:22pm UTC](https://discourse.paraview.org/t/problem-with-paraview-gitlab-master-build-on-linux/4996/5 "2020-08-13T16:22:38Z")

</div>

I found the issue with the Mesa version, but expect it to be in all version using internal Python builds.