# building version 5.7.0 on cluster (2)

**URL:** https://discourse.paraview.org/t/building-version-5-7-0-on-cluster-2/3489
**Category:** ParaView Support
**Created:** [February 3, 2020, 12:44pm UTC](https://discourse.paraview.org/t/building-version-5-7-0-on-cluster-2/3489 "2020-02-03T12:44:26Z")
**Posts on this page:** 1
**Showing post:** 4

<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: [February 14, 2020, 6:56am UTC](https://discourse.paraview.org/t/building-version-5-7-0-on-cluster-2/3489/4 "2020-02-14T06:56:50Z")

</div>

Do you have symlinks somewhere in your build dir path? Do they match the symlinks used in your source dir path?

If not, I suggest doing a `cd $(readlink -f $PWD)` to go to a path without any symlinks.

If that solves your problem, this is a long standing CMake behavior that is broader than it should be. [https://gitlab.kitware.com/cmake/cmake/issues/16228](https://gitlab.kitware.com/cmake/cmake/issues/16228) You can do any of:

- not use symlinks
- keep all symlinks common between your build and source tree
- reference symlink paths by their symlink-free name

to mitigate the issue.

---

_[View the full topic](https://discourse.paraview.org/t/building-version-5-7-0-on-cluster-2/3489)._