LinuxQuestions.org

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - libc.so.6 (https://www.linuxquestions.org/questions/debian-26/libc-so-6-a-4175495836/)

Hi guys,

New to debian, just installed 2 days ago. Im liking it and im planning on keeping it, but I am running into a issue that may cause me to go back to Ubuntu.

A software that I MUST have installed and working (for work) needs libc.so.6 to be 2.15+ but as far as I can see debian has 2.13 shipped in test and unstable, while 2.17 is in experimental.

/opt/gloCOM/bin/gloCOM: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /opt/gloCOM/bin/gloCOM)
/opt/gloCOM/bin/gloCOM: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.17' not found (required by /opt/gloCOM/bin/gloCOM)
/opt/gloCOM/bin/gloCOM: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /opt/gloCOM/lib/libgloox.so.8)
/opt/gloCOM/bin/gloCOM: /lib/i386-linux-gnu/i686/cmov/libm.so.6: version `GLIBC_2.15' not found (required by /opt/gloCOM/lib/libavcodec.so.55)

The question is, how can I safely update to 2.17 (or 2.15), what is the procedure?

If I do update to 2.17 (or 2.15) what can it break or can it cause other issues.

rebourn@laftof:/opt/gloCOM/bin$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 7.4 (wheezy)
Release: 7.4
Codename: wheezy

Thank in advanced.

Testing has 2.17, unstable 2.18:

Code:

$ apt-cache policy libc6

libc6:

  Installed: 2.17-97

  Candidate: 2.17-97

  Version table:

    2.18-1 0

          1 http://ftp.debian.org/debian/ unstable/main amd64 Packages

    2.18-0experimental1 0

          1 http://ftp.debian.org/debian/ experimental/main amd64 Packages

 *** 2.17-97 0

        500 http://ftp.debian.org/debian/ testing/main amd64 Packages

        100 /var/lib/dpkg/status

laca@laca-desktop:~$

Stable will never have anything newer than the one it has (2.13). You should either use testing/unstable or preload a newer libc (this worked using Ubuntu's libc when Steam requited 2.15 and Debian had 2.13).

Thanks!

Dumb question but, how would I go about using the Ubuntu's 2.15?

Update:

I updated libc from sid repo to 2.18. The software works beautifully, just wondering is there something I could break besides the mentioned software by running libc on 2.18 now.

Quote:

Originally Posted by rebourn (Post 5122726)

Update:

I updated libc from sid repo to 2.18. The software works beautifully, just wondering is there something I could break besides the mentioned software by running libc on 2.18 now.

You might break other stuff. But that you will find out yourself if it (hopefully not) happens...
I never had any issues after i upgraded to 2.17 from 2.13.

But beware: you ONLY should use testing/sid/experimental OR stable/stable-backports. DO NOT mix stable with anything else tha maybe the official backports.

Quote:

Originally Posted by gradinaruvasile (Post 5123007)

So apperantly im screwed now, considering I pulled just libc from sid and after removed it from the repo list?

Any chance on making this work?

Quote:

Originally Posted by rebourn (Post 5123135)

So apperantly im screwed now, considering I pulled just libc from sid and after removed it from the repo list?

Any chance on making this work?

As long as your systems and apps work, there are no problems obviously.