Actually, RHEL5 for x86_64 does come with a relatively full set of ia32 libraries, as did RHEL4. However, I don't think that will fix your real problem. If your program will run on an ia32 RHEL5 system, then it will most likely run on an x86_64 RHEL5 system as well. Your biggest problem is the need for the LD_ASSUME_KERNEL line, which indicates that you were actually running those programs in a compatibility mode even on RHEL3 and RHEL4.
You mention that only some of them need the LD_ASSUME_KERNEL setting. Have you tried the ones that don't need that? Also, have you tried using them on an x86_64 build of RHEL4? I suspect there are fewer problems with moving to x86_64 than you might think. We regularly use ia32 binaries on x86_64 on RHEL4 and RHEL5 with very few problems, as most of the libraries are already present by default. You could try a para-virtualized RHEL4 x86_64 on top of RHEL5 which would avoid issue #3. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vincent Cojot Sent: Tuesday, March 04, 2008 6:45 AM To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list Subject: [rhelv5-list] RHEL 5/x86_64 support for legacy x86 apps Hi everyone, At one of my customer sites, we use a number of 'legacy' custom-built graphical apps built with glibc-2.1. typically, these apps use X11, motif and.. OpenGL/GLX. Also, some of these apps require the use of the infamous "export LD_ASSUME_KERNEL=2.2.5" under RHEL3/RHEL4. But alas, the time has come to move to a newer RHEL along with an x86_64 kernel. Since they aren't ready to give up on these apps or re-build them (lack of engineering resources), I am left with the following transition options: 1) run a fully copy of RHEL4 x86 under VMWare server on every RHEL5/x86_64 workstation and export the app display to the native RHEL5 display using the network. 2) find a way to provide a full set of ia32 libraries under RHEL5 to enable those legacy apps on an x86_64 RHEL. 3) run the apps in a paravirtualized 32bit guest (but that's not supported/doable on RHEL 5.1, right?) 4) use the Solaris/SPARC version of those 32bit apps and get newer SPARC workstations since these apps run very fine on modern 64bit SPARC workstations under Solaris 10 and will continue to run under 11. - I fear that option 1) would eat up all of the resources very quickly. - On the other hand, I haven't noticed any official document on providing a full set of ia32 libs under the x86_64 version of RHEL5 like what exists on Solaris. - I heard the 'LD_ASSUMER_KERNEL' stuff is gone in RHEL5, is that true? - I'd like to avoid option 4) because of all the trouble in re-deploying just about everything. Any comments, ideas, relevant documents/links very welcomed. Thanks, Vincent S. Cojot _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
