I must correct myself. I found in /lib64 the subdirectory tls/ and it has dublicates of those libraries.
 
I guess the best solution in my situation would be to ask the system administrator to update this computer. The option for multiprocessor computers sounds very attractive and I would love to have it.
 
Thank you,
Vitaliy

 
> Date: Fri, 13 Aug 2010 22:35:28 +0100
> From: [log in to unmask]
> Subject: Re: 2.1.5 error
> To: [log in to unmask]
>
> Hello,
>
> I don't know what the tls means but I would guess that none of your libcs
> has the required GLIBC_2.6. So you could check:
>
> > strings /lib64/libc.so.6 | grep GLIBC
>
> And I would guess it only goes up to 2.4 or 2.5.
>
> Wayne
>
> On Fri, 13 Aug 2010, Vitaliy wrote:
>
> > actually this library I found in [vitaliyg@bbcsrv2 ~]$ ls -trl /lib64/libc*
> > -rwxr-xr-x 1 root root 17224 Feb 18 2005 /lib64/libcap.so.1.10
> > lrwxrwxrwx 1 root root 14 Nov 19 2007 /lib64/libcap.so.1 -> libcap.so.1.10
> > lrwxrwxrwx 1 root root 19 Nov 19 2007 /lib64/libcrypto.so.4 -> libcrypto.so.0.9.7a
> > lrwxrwxrwx 1 root root 11 Nov 19 2007 /lib64/libcap.so -> libcap.so.1
> > -rwxr-xr-x 1 root root 45488 Jul 24 2008 /lib64/libcrypt-2.3.4.so
> > -rwxr-xr-x 1 root root 198840 Jul 24 2008 /lib64/libcidn-2.3.4.so
> > -rwxr-xr-x 1 root root 1608008 Jul 24 2008 /lib64/libc-2.3.4.so
> > -rwxr-xr-x 1 root root 10384 Jul 25 2008 /lib64/libcom_err.so.2.1
> > lrwxrwxrwx 1 root root 13 Dec 10 2008 /lib64/libc.so.6 -> libc-2.3.4.so
> > lrwxrwxrwx 1 root root 17 Dec 10 2008 /lib64/libcrypt.so.1 -> libcrypt-2.3.4.so
> > lrwxrwxrwx 1 root root 16 Dec 10 2008 /lib64/libcidn.so.1 -> libcidn-2.3.4.so
> > lrwxrwxrwx 1 root root 17 Dec 10 2008 /lib64/libcom_err.so.2 -> libcom_err.so.2.1
> > -rwxr-xr-x 1 root root 1234328 Jan 14 2009 /lib64/libcrypto.so.0.9.7a
> >
> > But in the traceback the directory was /lib64/tls
> >
> > V.
> >