How to diagnosis and resolve: /usr/lib64/libz.so.1: no version information available

Question

Got sfclassi script and I am really new to php and html. I have to set it up and change its layout a bit, but the problem is there is nothing in its index file just a little code

require_once(dirname(__FILE__) . '/application/config/ProjectConfiguration.class.php');

$configuration=ProjectConfiguration::getApplicationConfiguration('cfclient', 'prod', false);
sfContext::createInstance($configuration)->dispatch();

Can some one explain what is happening here and how can I change its layout when I don't even have any html file

Solution 1

From What does the “no version information available” error from linux dynamic linker mean?, pertaining to libpam :

The "no version information available" means that the library version number is lower on the shared object. For example, if your major.minor.patch number is 7.15.5 on the machine where you build the binary, and the major.minor.patch number is 7.12.1 on the installation machine, ld will print the warning.

You can fix this by compiling with a library (headers and shared objects) that matches the shared object version shipped with your target OS. E.g., if you are going to install to RedHat 3.4.6-9 you don't want to compile on Debian 4.1.1-21. This is one of the reasons that most distributions ship for specific linux distro numbers.

Otherwise, you can statically link. However, you don't want to do this with something like PAM, so you want to actually install a development environment that matches your client's production environment (or at least install and link against the correct library versions.)

Solution 2

I have multiple version on my system and ran into the same issue. Under /usr/bin I created the python-2.4.3 file and pointed it to python which fixed my issue. the python-2.4.3 was erased some how after the compiling of my other versions that we are using. I believe that the yum application which is built within python 2.4.3 is the issue.

Comments

[Josue Figueiredo]

I never did find a working solution to this. Unfortunately, I have set this project aside for the past 10 months.

[Josue Figueiredo]

Yeah, that is exactly what I've looked at. I knew this is the problem, but I do not know what I need to do to fix this. I am guessing the culprit is this: /usr/lib64/libz.so.1 but from there I am not sure how to proceed. Thanks for giving this question at least a try.

[harrymc]

The possible fixes were listed above : (1) recompile your product using a lower-level library, (2) link your product statically so as not to use the local shared version. I don't see a 3rd solution, but maybe someone else here will.

[slhck]

Please learn to use the formatting tools available for your answers, thank you.