# ParaView 5.11-0 RC1 binary fails on CentOS 7: GLIBC\_2.25 not found

**URL:** https://discourse.paraview.org/t/paraview-5-11-0-rc1-binary-fails-on-centos-7-glibc-2-25-not-found/10263
**Category:** ParaView Support
**Created:** [September 7, 2022, 2:48pm UTC](https://discourse.paraview.org/t/paraview-5-11-0-rc1-binary-fails-on-centos-7-glibc-2-25-not-found/10263 "2022-09-07T14:48:46Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![jmensmann](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jmensmann/32/6141_2.png) [@jmensmann](https://discourse.paraview.org/u/jmensmann)
#### Post date: [September 7, 2022, 2:48pm UTC](https://discourse.paraview.org/t/paraview-5-11-0-rc1-binary-fails-on-centos-7-glibc-2-25-not-found/10263/1 "2022-09-07T14:48:46Z")

</div>

Is CentOS 7 still a supported platform for the binary release?

```auto
/test/ParaView-5.11.0-RC1-MPI-Linux-Python3.9-x86_64/bin$ ./paraview
/test/ParaView-5.11.0-RC1-MPI-Linux-Python3.9-x86_64/bin/paraview-real: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /test/ParaView-5.11.0-RC1-MPI-Linux-Python3.9-x86_64/bin/../lib/../lib/libHoloPlayCore.so)
/test/ParaView-5.11.0-RC1-MPI-Linux-Python3.9-x86_64/bin/paraview-real: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /test/ParaView-5.11.0-RC1-MPI-Linux-Python3.9-x86_64/bin/../lib/../lib/libHoloPlayCore.so)
/test/ParaView-5.11.0-RC1-MPI-Linux-Python3.9-x86_64/bin/paraview-real: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /test/ParaView-5.11.0-RC1-MPI-Linux-Python3.9-x86_64/bin/../lib/../lib/libHoloPlayCore.so)

```

Works fine on Ubuntu 20.

`libHoloPlayCore.so` seems to be the only library requiring the newer glibc:

```auto
/test/ParaView-5.11.0-RC1-MPI-Linux-Python3.9-x86_64/lib$ objdump -T libHoloPlayCore.so | grep GLIBC_2.25
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.25 getrandom
/test/ParaView-5.11.0-RC1-MPI-Linux-Python3.9-x86_64/lib$ objdump -T *.so | grep GLIBC_2.25
0000000000000000 DF *UND* 0000000000000000 GLIBC_2.25 getrandom

```

---

<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: [September 7, 2022, 3:59pm UTC](https://discourse.paraview.org/t/paraview-5-11-0-rc1-binary-fails-on-centos-7-glibc-2-25-not-found/10263/2 "2022-09-07T15:59:28Z")

</div>

It’s on our radar. We need to have HoloPlayCore not load by default.

---

<div class="post-metadata">

### Author: ![heksel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/h/4491bb/32.png) [@heksel](https://discourse.paraview.org/u/heksel)
#### Post date: [October 5, 2022, 5:56am UTC](https://discourse.paraview.org/t/paraview-5-11-0-rc1-binary-fails-on-centos-7-glibc-2-25-not-found/10263/3 "2022-10-05T05:56:17Z")

</div>

I can confirm that faced the same issue with CentOS 7.

---

<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: [October 5, 2022, 5:01pm UTC](https://discourse.paraview.org/t/paraview-5-11-0-rc1-binary-fails-on-centos-7-glibc-2-25-not-found/10263/4 "2022-10-05T17:01:07Z")

</div>

RC2 should have the problem avoided.

---

<div class="post-metadata">

### Author: ![Alex\_Sunny](https://discourse.paraview.org/user_avatar/discourse.paraview.org/alex_sunny/32/10854_2.png) [@Alex\_Sunny](https://discourse.paraview.org/u/Alex_Sunny)
#### Post date: [February 7, 2023, 4:12pm UTC](https://discourse.paraview.org/t/paraview-5-11-0-rc1-binary-fails-on-centos-7-glibc-2-25-not-found/10263/5 "2023-02-07T16:12:11Z")

</div>

> [@ben.boeckel](#):
>
> It’s on our radar. We need to have HoloPlayCore not load by default.  
> [Ometv](https://ometv.onl) [chatroulette](https://chatroulette.top)

thanks my issue has been fixed.