How can I update GLIBC to 2.27 and get rid of the above error?
While it's possible to do, there are some disadvantages:
- If you make any mistake in the process, you will render the system un-bootable. Better have recovery media ready and know how to use it to manually mount your root filesystem and repair it.
- While GLIBC is highly backward compatible, existing programs that depend on undefined behavior may break.
Your best bet is to run this new program in a chroot
environment or in a docker container.
Your next best bet is to install GLIBC-2.27 in parallel with system GLIBC, as described in e.g. this answer.
If you do decide to update the system GLIBC to the new version, the least error-prone way to do so is to download a new package, boot the system from recovery media, mount root filesystem on e.g. /mnt
, and unpack the new version on top of it.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…