glibc

Compute
Bell User Guide
Weber User Guide
Gilbreth User Guide
Scholar User Guide
Geddes User Guide
Hammer User Guide
Anvil User Guide
Negishi User Guide
Datasets
iGenomes
Software Catalog
Compilers
MPIs
Applications
Utilities
Biocontainers
NVIDIA NGC containers
AMD ROCm containers
FAQs
- AMD GPUs in Bell and Negishi
- Using constraint to request specific GPUs
- MPI
- R
- Many-Task Computing using hyper-shell
- Julia package installation
- Jupyter kernel creation
- Disk quota exhausted
- glibc
- Large memory jobs
- Custom Software Installation
Storage
Data Depot User Guide
Fortress User Guide
REED Folder User Guide
Box Research Lab Folder User Guide
Scratch User Guide
Home Directory User Guide
Services
High-Performance Computing
Services Guides
Slurm
Environment Management with the Module Command

glibc

When you try to install some software on clusters, the installation may fail due to reasons similar to this: "XX requires libc version 2.27 or at least 2.23, but the current version is 2.17". Unfortunately, glibc is bundled with the operation system, and we cannot update it for you.

To check the version of glibc on our cluster, you can run the below command:

$ ldd --version
ldd (GNU libc) 2.17
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.

Link to section 'Workaround' of 'glibc' Workaround

Singularity containers
Install an older version of your software

Helpful?