Enterprise Linux 8 (Red Hat, Centos Stream, AlmaLinux, Rocky Linux, Oracle Linux etc)

• Dec 16, 2022 - 22:20
$ ./MuseScore-4.0.0-x86_64.AppImage 
/lib64/libjack.so.0
/lib64/libnss3.so
/tmp/.mount_MuseSc9LSxL6/bin/mscore4portable: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_MuseSc9LSxL6/bin/mscore4portable)
/tmp/.mount_MuseSc9LSxL6/bin/mscore4portable: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by /tmp/.mount_MuseSc9LSxL6/bin/mscore4portable)
/tmp/.mount_MuseSc9LSxL6/bin/mscore4portable: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_MuseSc9LSxL6/bin/../lib/libsndfile.so.1)
/tmp/.mount_MuseSc9LSxL6/bin/mscore4portable: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_MuseSc9LSxL6/bin/../lib/libFLAC.so.8)
$ strings /lib64/libm.so.6 | grep GLIBC_2.2[0-9]
GLIBC_2.23
GLIBC_2.24
GLIBC_2.25
GLIBC_2.26
GLIBC_2.27
GLIBC_2.28
$ strings /lib64/libstdc++.so.6 | grep GLIBCXX_3.4.2[0-9]
GLIBCXX_3.4.20
GLIBCXX_3.4.21
GLIBCXX_3.4.22
GLIBCXX_3.4.23
GLIBCXX_3.4.24
GLIBCXX_3.4.25

Is it possible to build mscore-4 for these versions of glibc and glibcxx?


Comments

In reply to by romanbogatov

I think creating a GitHub profile is as simple as what you did to get an account here on MuseScore. Who knows what the MS developers and admins decide for platform support. Once us end-users venture into building software on a Linux platform, it becomes a walk-through-the-minefield. You can also think about posing your build questions/errors to a message forum for the particular Linux you're building on.

Is there a reason you can't install those updated versions on your system? It seems your current installation stopped just right before them.

In reply to by jeetee

> Is there a reason you can't install those updated versions on your system?

Yes, there are reasons. In systems of this type (RHEL and clones in this case), it is impossible to update such components at will, this will inevitably break the system in some respect. Such components should remain unchanged throughout the life of the distribution. The only regular way to get a newer version of GLIBC is to install a new version of the distribution or another Linux distribution.

Software developers are well aware of this and rely on the current versions of stable distributions such as RHEL and Debian. The version of the distribution on which this MS4.AppImage does not work will be relevant until 2029, which is why I created this post more out of surprise than in the hope of getting help.

Do you still have an unanswered question? Please log in first to post your question.