On Mon, 3 Jun 2013, Dave Reisner wrote:

> On Mon, Jun 03, 2013 at 04:56:08PM +0000, Gopikrishnan Balasubramanian -X (gopbalas - HCL TECHNOLOGIES LIMITED at Cisco) wrote:
>> Hi Petr,
>>
>> I have checked my build system. Its not there anywhere in the server.
>>
>> Please have a look.
>> [root_at_vqe-vm iso]# ll /usr/local/
>> total 40
>> drwxr-xr-x. 2 root root 4096 May 3 18:57 bin
>> drwxr-xr-x. 2 root root 4096 Jun 28 2011 etc
>> drwxr-xr-x. 2 root root 4096 Jun 28 2011 games
>> drwxr-xr-x. 2 root root 4096 Jun 28 2011 include
>> drwxr-xr-x. 2 root root 4096 Jun 28 2011 lib
>> drwxr-xr-x. 3 root root 4096 May 3 18:46 lib64
>> drwxr-xr-x. 2 root root 4096 Jun 28 2011 libexec
>> drwxr-xr-x. 2 root root 4096 Jun 28 2011 sbin
>> drwxr-xr-x. 6 root root 4096 May 3 18:46 share
>> drwxr-xr-x. 2 root root 4096 Jun 28 2011 src
>> [root_at_vqe-vm iso]# cd /usr/local/lib64/
>> [root_at_vqe-vm lib64]# ll
>> total 4
>> drwxr-xr-x. 5 root root 4096 May 3 19:00 perl5
>> [root_at_vqe-vm lib64]# cd /usr/local/lib/
>> [root_at_vqe-vm lib]# ll
>> total 0
>> [root_at_vqe-vm lib]#
>>
>> Is there a way to bypass this issue. I did a symbolic link to libcurl.so.4, but it did not work.
>
> No, this is entirely the wrong thing to do. They're numbered as such
> because they're incompatible with each other. You see what the linker
> includes in the execution and where it comes from, e.g.
>
> $ LD_DEBUG=files curl
> ...snipped...
> 22401: calling init: /usr/lib/libcurl.so.4
> ...snipped...
>
> You really do need to find the rogue libcurl.so.3.

Is it definitely a rogue libcurl.so.3? Could it not be code that has a
dependecy on libcurl.so.3 that's been linked in?

jh
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ: http://curl.haxx.se/docs/faq.html
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2013-06-03