Binary compatibility issue between RH EL4 and RH EL5 (SIGFPE: Floating Point Exceptio
Red HatThis forum is for the discussion of Red Hat Linux.
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.
Copying dd from RHEL4 and running on RHEL5 ran successfully when just copying the binary, as well as when packaged with RHEL4's libc and ld-linux. Due to some crazy company policy restrictions, I packaged these by hand rather than using stratifier or Ermine.
Happily, though, I have realized that we have another alternative that karhel didn't: we are building the applications that need to run on multiple distributions/versions. Because of this, we're going to investigate the possibility of building on a newer version and verifying compatibility on older ones.
Thanks for the thoughts! I'm very impressed by getting a response on this thread! I will definitely post the results of our further attempts.
Good to know. Thanks for the update (and nice memory)! Things are good for us building on RHEL5, packaging necessary shared objects (including ld-linux), and then running on RHEL4 (and others). Still curious why going the other way doesn't seem to work, but we'll be content with this approach.
Thanks again!
Last edited by fion; 06-27-2014 at 12:45 PM.
Reason: More firm claim on how we're moving forward
Good to know. Thanks for the update (and nice memory)! Things are good for us building on RHEL5, packaging necessary shared objects (including ld-linux), and then running on RHEL4 (and others). Still curious why going the other way doesn't seem to work, but we'll be content with this approach.
Looks like the problem boils down to the following: ld.so on RHEL5 uses ONLY GNU_HASH.
This section is not present in executables built for RHEL4, so ld.so can't find information
it supposed to find.
Actually, I had found that stackoverflow topic as well. Unfortunately, I didn't really understand what they were talking about well enough for me to implement any change. What is "readelf" really being run on? What did it mean to "look for a GNU_HASH"? When I ran readelf on my executable, I couldn't find GNU_HASH in the results anywhere. Which, I suppose, wasn't surprising.
Then, the build options that were recommended ... are those compiler or linker options? I believe they're compiler options. However, I didn't have the motivation to try them, since our build environment is pretty crazy. Switching platforms was simpler than adding compiler options. :/
Still, because I'm impressed by the help I've received, I tried compiling one of our applications with -Wl,--hash-style=both on RHEL4. This resulted in an error:
/usr/bin/ld: unrecognized option '--hash-style=both'
Same error with sysv:
/usr/bin/ld: unrecognized option '--hash-style=sysv'
So, again, I'm not quite sure what's going on. But I am content with building on RHEL5, as that build runs everywhere that we need it to.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.