Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

195
Views
How can I link to an older version of a shared library

I'm building my program on my computer, on which libtiff.so -> libtiff.so.5. And then pushing the builds on another machine on which libtiff.so -> libtiff.so.4.

At runtime, my program exists : « error while loading shared libraries: libtiff.so.5: cannot open shared object file: No such file or directory ».

I cannot upgrade the other machine, and I would like to avoid compiling on a virtual machine (with the same linux version than the executing machine). Therefore, I would like to force the compiler to use the libtiff.so.4 instead of libtiff.so.5.

I have libtiff.so.4 installed on my computer (as well as libtiff.so.5). How can I force the linkage with this version instead of the newer version. I thought about moving the libtiff.so -> libtiff.so.4, but I'm afraid of breaking my system if it needs the latest version (apt-get purge libtiff5 gives an error because some other package needs it).

Is it possible to link with an older (installed) version of a library? If yes, how? And is it harmfull to change the symbolic link of libtiff.so to the older version? If not, will it solve my issue?

over 4 years ago · Santiago Trujillo
3 answers
Answer question

0

You can use this syntax to link to a specific version of a library:

gcc [other options] -l:libtiff.so.4

You do not need to specify a path; the usual directories are searched in order to find the library.

Note: as Michael Wild mentioned, you should have the header files for that version installed instead of the newest ones.

over 4 years ago · Santiago Trujillo Report

0

As others have mentioned, you can force the linker by specifying the full versioned name, or even the absolute path.

However, I would strongly advice against doing so. The problem is, that the installed headers correspond to the newer version of the library. If there have been API/ABI-breaking changes between these library versions, the program might work, crash intermittently, or if you're lucky, not work at all.

Instead you should temporarily install the development package that corresponds to the libtiff.so.4 library. If on Debian/Ubuntu or similar, this would be the libtiff4-dev package.

over 4 years ago · Santiago Trujillo Report

0

Specify the full path to the .so: instead of -ltiff pass /lib64/libtiff.so.4 to the linker.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!