Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am in very much need to resolve the issue of Upgrade redhat5 from glibc 2.5 to glibc 2.7. The problem is when I run a binary compiled on our build setup (glibc 2.11) on Suse 11 (glibc 2.9) it works fine...
But the same binary do not work on redhat enterprise version 5 telling error as need glibc2.7 or sometimes segmentation fault for the same binary execution.
I tried upgrading the redhat glibc 2.5 to glibc 2.7, but not successful.
I am really worried about this issue.
You can't. Or, you probably could, but it's a very bad idea. glibc is very tightly tied to the rest of the system and changing major versions will probably break everything. You need to build your binary differently.
The normal way to overcome this problem is to build the application on the platform with the lowest version of the library. That means you should build it on the RHEL5 system and use it on Suse.
The normal way to overcome this problem is to build the application on the platform with the lowest version of the library. That means you should build it on the RHEL5 system and use it on Suse.
Seconded. Usually the more ancient Linux used for build server the more portable executable will be.
If you have difficult moving build server to RHEL5 you can try statifier (http://statifier.sf.net) or Ermine (http://magicErmine.com)
Both of them create self-contained executable that not depend on present of specific version of shared library
You can't. Or, you probably could, but it's a very bad idea. glibc is very tightly tied to the rest of the system and changing major versions will probably break everything. You need to build your binary differently.
Maybe it is... But there are many articles that it is possible to upgrade glibc2.5 to glic2.7 on RHEL5.X using "up2date glibc" command.
Actually, I 've to upgrade glibc2.5 to glibc2.9 on RHEL5.x. The following upgrade is impossible?
Maybe it is... But there are many articles that it is possible to upgrade glibc2.5 to glic2.7 on RHEL5.X using "up2date glibc" command.
Actually, I 've to upgrade glibc2.5 to glibc2.9 on RHEL5.x. The following upgrade is impossible?
Then maybe you should post to those articles, or follow their advice (at your own risk...).
I would very much doubt those articles, because RHEL 5 uses yum, not up2date.
You can "yum upgrade glibc" all you want .. you're only going to get glibc 2.5 on RHEL 5.
Again -- bad idea. Feel free to find another way, at your own risk, though.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Upgrade redhat5 from glibc 2.5 to glibc 2.7
