In Ubuntu10.04, iNodeClient runs install. sh and the installation is successful. In Ubuntu12.04, you cannot run it after double-clicking iNodeClient. The problem persists after reinstallation. Run the command line. It indicates libjpeg. so.62notfound. So I searched for information online and found this article, and found that the method in this article was a bit complicated. In addition to searching for dependencies and locating library files, you also need to copy the library files to the current directory.
When iNodeClient is running Ubuntu 10.04, install. sh is successfully installed. In Ubuntu 12.04, double-click iNodeClient after installation, but it cannot run. The problem persists after reinstallation. Run the command line. The prompt says libjpeg. so.62 not found.
So I searched for information online and found this article, and found that the method in this article was a bit complicated. In addition to searching for dependencies and locating library files, this method also needs to copy the library files to the current directory and then create soft links, which is tedious. In fact, you only need to directly establish soft links and do not need to perform replication. In addition, it is not a good habit for the author to use sudo too much.
Summarize my practices first.
1. Unsatisfied dependencies are found. Assume that the iNode installation directory is :
Www.linuxidc.com @ linuxidc ~ Ldd /INodeClient | grep 'not found'
This line of code has two roles. The first is to find the dependency that is not satisfied when running iNodeClient; the second is to check the location of the library that iNodeClient depends on (because different libraries may exist in multiple places ). On my machine, I found that two libraries could not be found: libjpeg. so.62 and libtiff. so.3. The link is the introduction of the two libraries wikipedia.
In addition, iNodeClient library dependencies are found in the/usr/lib/i386-linux-gnu/directory (I installed a common 32-bit version, other versions may be different ).
2. check whether these databases exist locally. Because the operating system version is updated, the accompanying libraries may also be updated. This will change the name of the Library version, and this may be one reason why the dependency is "not satisfied. This type of "unsatisfied" comes from different names. In fact, newer libraries exist. The following command is used to find the location of the local database with the same name.
Www.linuxidc.com @ linuxidc ~ Locate libjpeg
We found that these libraries are actually available locally. And exists under the/usr/lib/i386-linux-gnu/directory.
3. Create a soft link. There are two libjpeg files in the/usr/lib/i386-linux-gnu/directory, one is libjpeg. so.8, and the other is libjpeg. so.8.0.2. After playing with LFS, experience tells me that libjpeg. so.8 is a soft link to libjpeg. so.8.0.2. It may be created for minor version updates without affecting the library usage of the program. So I chose to link to libjpeg. so.8 to get this little convenience. This sentence is the only place where sudo needs to be used to obtain permissions.
Www.linuxidc.com @ linuxidc ~ Sudo ln-s/usr/lib/i386-linux-gnu/libjpeg. so.8/usr/lib/i386-linux-gnu/libjpeg. so.62
With these three steps, you can solve the problem of the first database.
The solution for the second database is the same. The following is the code.
Www.linuxidc.com @ linuxidc ~ Sudo ln-s/usr/lib/i386-linux-gnu/libtiff. so.4/usr/lib/i386-linux-gnu/libtiff. so.3
After the dependency problem is solved, iNodeClient can be used.