LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   dlopen error: libc.so.6: version 'GLIBC2.14' not found (https://www.linuxquestions.org/questions/linux-software-2/dlopen-error-libc-so-6-version-glibc2-14-not-found-4175537248/)

kathbeau 03-19-2015 10:25 AM

dlopen error: libc.so.6: version 'GLIBC2.14' not found
 
I requested a copy of a custom .so from a colleague, to spare myself the hassle of writing a makefile and building it myself. (I have the source code, but the library was created by a Windows programmer, so building for Linux is a DIY project.)

I am running:
Linux mix 3.16-0.bpo.2-amd64 #1 SMP Debian 3.16.3-2~bpo70+1 (2014-09-21) x86_64 GNU/Linux

My colleague says the library was built on Ubuntu Server 12.04 LTS.

Trying to load it in my environment yields this error:

/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /usr/lib/libcstage0205.so)"

Have I forgotten to mention that I'm a Linux newbie? So I'm kind of fumbling here.

QUESTION #1:
When I look at the properties for my copy of /lib/x86_64-linux-gnu/libc.so.6, it says it points to libc-2.13.so. Does that have anything to do with the 'GLIBC_2.14' not found?

QUESTION #2:
I'm going to try writing the makefile (whimper) and build the library myself, but it leaves me wondering: How could I distribute a custom .so (binary) without releasing source code?

Thanks for your assistance in my continuing education.

Kathleen

veerain 03-19-2015 11:41 AM

Quote:

When I look at the properties for my copy of /lib/x86_64-linux-gnu/libc.so.6, it says it points to libc-2.13.so
So you have only glibc-2.13 library. The one your friend gave needs glibc-2.14 atleast, that's why the error.

You should always use same distro/version for such things. Else there may be binary incompatibilities leading to errors.

kathbeau 03-19-2015 11:53 AM

Quote:

Originally Posted by veerain (Post 5334706)
So you have only glibc-2.13 library. The one your friend gave needs glibc-2.14 atleast, that's why the error.

You should always use same distro/version for such things. Else there may be binary incompatibilities leading to errors.

Thank you for confirming my hunch.

This still leaves me with the question of how I can distribute an application that relies upon a custom .so. Will I always have to provide MAKE files and source code and tell the customers to build the library themselves?

Kathleen

veerain 03-19-2015 12:14 PM

Quote:

This still leaves me with the question of how I can distribute an application that relies upon a custom .so. Will I always have to provide MAKE files and source code and tell the customers to build the library themselves?
Most of guys distributing binaries usually package them and release for specific distros/versions. But LSB (Linux Standards Base) solves this problem somewhat. Read about it.

kathbeau 03-19-2015 12:34 PM

Quote:

Originally Posted by veerain (Post 5334734)
Most of guys distributing binaries usually package them and release for specific distros/versions. But LSB (Linux Standards Base) solves this problem somewhat. Read about it.

Thank you so much! I'll start reading, and will see if I can make this work for us.

Kathleen


All times are GMT -5. The time now is 10:59 PM.