Old libs, New libs
I am trying to run some s/w that requires new libs (glibc2.4) but I do not have it. I am running Centos 4.7 and for technical reasons I cannot upgrade it. So, I was wondering If I could drop the required libs in or not. (without changing anything else)
mike |
No.
|
Old libs, new libs, red libs, blue libs.
In all seriousness I think a bigger concern is your difficulties upgrading to a more recent release of CentOS. They may have a long support cycle but this distro does not like to backport. |
I do not have trouble going to a newer distro. My base workstation is used to compile simulations that run on a thousand node cluster! And the cluster is at 4.7. So, I can't just upgrade.
I guess I will just build a OS disk to deal with the problem (latest release). Thanks Mike |
Quote:
|
Well - you can't. That's the answer to your question; it's short and to the point. You were looking for a longer explanation, I gather?
You can't because glibc is a too important part of the system. If you tried e.g. building it yourself, you run a big risk of hosing your system. glibc is the standard GNU C library. CentOS doesn't have a newer version available for version 4, and it doesn't backport much. However distros often provide glibc compatibility libs for older glibcs - see the compat-glibc package(s). |
I do prefer reasoned answers... guessing most would. And thank you. I suspected it was a bad idea, just wondered. I will install a recent OS version in an attempt to get to the bottom of my problem.
Thanks, Mike |
Quote:
build your application here, and then use statifier (http://statifier.sf.net) or Ermine (http://magicErmine.com) to build self-containing executable. This executable (single file) you can use on your cluster with CentOS 4.7. Please note that you build OS shouldn't be too recent - otherwise resulting executable will not run on CentOS4.7 |
All times are GMT -5. The time now is 12:04 PM. |