/usr/lib64/libc.so.6: version `GLIBC_2.34' not found Error after trying minisplice and miniprot_boundary_scorer

[desmodus1984]

Hi,
I tried generating hints using proteins, and I got a very similar error while trying to run minisplice and miniprot_boundary_scorer.
For minisplice I got this error:
/data/common/juanpablo.aguilar/apps/minisplice/minisplice: /usr/lib64/libm.so.6: version GLIBC_2.29' not found (required by /data/common/juanpablo.aguilar/apps/minisplice/minisplice) /data/common/juanpablo.aguilar/apps/minisplice/minisplice: /usr/lib64/libm.so.6: version GLIBC_2.27' not found (required by /data/common/juanpablo.aguilar/apps/minisplice/minisplice)
/data/common/juanpablo.aguilar/apps/minisplice/minisplice: /usr/lib64/libc.so.6: version `GLIBC_2.34' not found (required by /data/common/juanpablo.aguilar/apps/minisplice/minisplice)

and then for miniprot_boundary_scorer:
/data/common/juanpablo.aguilar/apps/miniprot-boundary-scorer/miniprot_boundary_scorer: /usr/lib64/libm.so.6: version GLIBC_2.29' not found (required by /data/common/juanpablo.aguilar/apps/miniprot-boundary-scorer/miniprot_boundary_scorer) /data/common/juanpablo.aguilar/apps/miniprot-boundary-scorer/miniprot_boundary_scorer: /usr/lib64/libc.so.6: version GLIBC_2.34' not found (required by /data/common/juanpablo.aguilar/apps/miniprot-boundary-scorer/miniprot_boundary_scorer)

I ran miniprot, minisplice and miniprot_boundary_scorer inside a conda environment, hoping to avoid problems due to missing programs or incompatible ones since I work on an HPC with PBS system. I tried running GALBA but it failed, and since I want to annotate a genome, and I am already running Tiberius, I thought on generating some hints for Augustus, to then use as evidence to run EvidenceModeler.

Thanks.

[dpryan79]

Which linux distribution and version is on your cluster?

[desmodus1984]

Hope this information is enough:

LSB Version: n/a
Distributor ID: AlmaLinux
Description: AlmaLinux 9.6 (Sage Margay)
Release: 9.6
Codename: n/a

[dpryan79]

Somehow it appears there's a much much much older glibc installed on the cluster nodes (that version of alma linux should already have GLIBC_2.34). Maybe contact your cluster admins? This is unfortunately not an issue we can address.