LinuxQuestions.org - dependency error: libc.so.6

- Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)

- - dependency error: libc.so.6 (https://www.linuxquestions.org/questions/linux-software-2/dependency-error-libc-so-6-a-4175423201/)

dependency error: libc.so.6

Hi,
i'm trying download tdsodbc package but exist a dependency error with file libc.so.6.

I've tried dowload glibc_2.14 but exist more dependency error again, although these packages are installed already. Do install glibc_2.11.3 now? Or is this package installed already? Command "zypper" (apt-get for Suse) doesn't find tdsodbc package.

I don't know that I have to do...
Any idea, please?

Thanks!!

Quote:

have you got a 64 bit libc.so.6?

Quote:

bash-4.1$ ls -l /lib/libc.so.6
lrwxrwxrwx 1 root root 12 Dec 29 2011 /lib/libc.so.6 -> libc-2.13.so
bash-4.1$ ls -l /lib64/libc.so.6
lrwxrwxrwx 1 root root 12 Dec 29 2011 /lib64/libc.so.6 -> libc-2.13.so

Yes, I have got a 64 bit libc.so.6:

Quote:

$$ ls -l /lib64/libc*
-rwxr-xr-x 1 root root 1754140 may 24 17:03 /lib64/libc-2.11.3.so
lrwxrwxrwx 1 root root 14 jun 11 16:11 /lib64/libcap.so.2 -> libcap.so.2.11
-rwxr-xr-x 1 root root 19016 nov 5 2011 /lib64/libcap.so.2.11
-rwxr-xr-x 1 root root 197092 may 24 17:03 /lib64/libcidn-2.11.3.so
lrwxrwxrwx 1 root root 17 jun 11 17:34 /lib64/libcidn.so.1 -> libcidn-2.11.3.so
lrwxrwxrwx 1 root root 17 jun 11 16:11 /lib64/libcom_err.so.2 -> libcom_err.so.2.1
-rwxr-xr-x 1 root root 14720 feb 3 2012 /lib64/libcom_err.so.2.1
-rwxr-xr-x 1 root root 57699 may 24 17:03 /lib64/libcrypt-2.11.3.so
lrwxrwxrwx 1 root root 22 jun 11 16:15 /lib64/libcryptsetup.so.0 -> libcryptsetup.so.0.0.0
-rwxr-xr-x 1 root root 56440 feb 3 2012 /lib64/libcryptsetup.so.0.0.0
lrwxrwxrwx 1 root root 18 jun 11 17:34 /lib64/libcrypt.so.1 -> libcrypt-2.11.3.so
lrwxrwxrwx 1 root root 14 jun 11 17:34 /lib64/libc.so.6 -> libc-2.11.3.so

Is this good? How should I proceed?

Well, one thing is sure, you cannot use a Suse 12 package in SLED11.

And : glibc is your OS (together with the kernel).
→ → glibc cannot be changed. ( from 2.11 to 2.14 ).

Suggest :
Build the rpm packages for your OS by using the source code
SRC.RPM, e.g. the Suse 12 freetds-0.91-2.1.2.src.rpm .
( libtdsodbc0 etc. etc.)

Or ask your Suse support. ( Looks like you have a license.)

.

Try these lines (the second if the first doesn't work)

LD_PRELOAD=/lib64/libc.so.6 rpm -Uvh libtdsodbc0-0.91-2.1.2.x86_64.rpm
LD_LIBRARY_PATH=/lib64 rpm -Uvh libtdsodbc0-0.91-2.1.2.x86_64.rpm

If they don't do it, let's take stock. You have rpm, but you're not using yum.

Whose rpm is it (e.g. fedora 13)
What's your distro?
Why not use yum?

There are options for rpm that effectively allow you to give the middle finger to it's safety side if you know what you're doing, but I'm not sure you do.

Suse : No 'yum'. But 'zypper'. Quote from post # 1 :

Quote:

Command "zypper" (apt-get for Suse) doesn't find tdsodbc package.

And : there seem to be no *tds* packages for SLES 11.

Then if he really wants to play with it, with some clever options from the rpm man page he can install it in ~/ .