I am running an app which requires glibc 2.26-lp150.9.1. Subsequent versions cause the app to crash with a segmentation fault. It is uncertain when the developers will fix the problem. That said, is it possible to update the system to the lated glibc (17.1) while installing the obsolete version also so that this app alone will use the older version?
Thanks.
You would need to put the older version of glibc in a different directory. And then you would need to run your application with LD_LIBRARY_PATH set to include that directory.
Depending on what you are doing, you might also need the header files associated with the older version.
If it is practical, it might be easier to setup a virtual machine with the older glibc, and run your application in that virtual machine.
Thanks, I’ll try the LD_Lib path idea. The virtual machine thing won’t work as this is a backup program which needs to access my real machine with the proper relevant file structure.
In this case, please make sure your restore-from-backup functionality still works.
I vaguely remember horror stories where outdated and/or bug-ridden (and probably closed-source/proprietary) backup software barely managed to run regular backups, but then failed to be able to restore a system after a fatal crash occured. In my opinion, the safest long-term option would be to use a well-supported, up-to-date and free alternative like Déjà Dup or Bareos.
Yes, that’s an important point.