[SOLVED] How to configure system for software to use older libraries.

CowboyRT · 06-24-2014, 01:19 PM

I am currently running CentOS 6.5. The software I'm attempting to install on CentOS 6.5 was supported on CentOS 4.x, thus it depends on the 2.3 version of glibc and 3.4 version of libstdc++. I want to know first is it possible to install these older libraries in a custom directory like /opt/appName/bin.

If installing these old libs in a custom directory works, what would be the best way to get the software to see these old libraries in the custom directory? Do I point to the old libraries using a .conf file in ld.so.conf.d? Since all of the software's binaries are initiated by a script, do I use LD_LIBRARY_PATH to point to the custom directory in all of the scripts.

Thanks in advance.
CowboyRT

jdkaye · 06-25-2014, 12:16 AM

If you've paid for RHEL then you are entitled to support from them. Why not contact them and I'm sure they can sort you out. If you haven't paid for RHEL then you might consider using CentOS.
jdk

John VV · 06-25-2014, 01:31 AM

if can be done but EXTREME CAUTION !!!! must be taken !!!

contact redhat tech support for guidance

a small mistake could KILL your 6.5 install very very fast and to the point that reinstalling might be easier

CowboyRT · 06-25-2014, 11:21 AM

Sorry folks. I cannot believed I typed that. I am running CentOS 6.5 and not RHEL 6.5. Will edit my post. Surely, I would have contacted them if I were running that distro.

Regards,
CowboyRT

John VV · 06-25-2014, 10:18 PM

the first thing you will need to do is install the legacy gcc 34

Code:

su -
yum search gcc 
------------- then from that list should be 34--------------------
yum install compat-gcc-34 compat-gcc-34-c++

gcc 3.4 should be old enough it is what was in the cent 4.9 repo

then you have to install things where the OS CAN NOT!!!!! FIND THEM!!!!!!!
the build folder CAN NOT be in the $PATH and libs can NOT be in $LD_LIBRARY_PATH

Warning: that is VERY IMPORTANT!!!!!!!
cent6 can NOT see nor find or use any of the old programs !!!!!!!!
ONLY the program you are building can use them !!!!!!!!!!!

now
expect something like this a FULL WEEK if you know what you are doing and have done it many times

you are about to hit what is called " Dependency HELL!!!"
and it is apply named

glibc 2.3 will need a ton of dependency's

so make a folder someplace ???
like
/usr/opt/TheProgramName/dep

replace"TheProgramName" with the real name
and install the dependency's into that "dep" folder
and PASS that location to the compiler for all the libs and and all the paths including packageconf *.pc files

this is best done using a build shell script because the "configure" and exports to "make" are going to get VERY LONG

this will take time

you might want to install KVM and install the dead and unsupported CentOS 4.9 into the KVM VM
that might be easier
just KEEP IT OFF LINE !!!!!!
4.9 has been unsupported for some time

CowboyRT · 06-26-2014, 04:42 PM

John VV, thanks for the feedback. I sort of figured I had to hide libs from the OS, but I totally forgot about having to deal with the dependencies. It's going to take some time, but I'll post whether I'm successful or not. I feel confident this is the correct approach so I'm marking my inquiry as solved.