SCIENTIFIC-LINUX-USERS Archives

April 2015

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Steven Haigh <[log in to unmask]>
Reply To:
Steven Haigh <[log in to unmask]>
Date:
Tue, 28 Apr 2015 09:31:04 +1000
Content-Type:
multipart/signed
Parts/Attachments:
text/plain (777 bytes) , signature.asc (834 bytes)
On 28/04/2015 7:07 AM, Ken Teh wrote:
> I have a user who has installed an executable built on a other Linux
> distro.  Claims it was built on a 64-bit linux (doubtful).  He has no
> problems running it on a 32-bit SL6.x machine but cannot run it on a
> 64-bit SL6.x machine.  Chokes with the following:
> 
> ...:/lib/ld-linux.so: bad ELF interpreter: No such file or directory.
> 
> I'm wondering if it is "safe" to add a symbolic link to the
> ld-linux-x86_64.so.2 to fix this.

/lib/ld-linux.so is a 32 bit library. The 64 bit libraries are usually
in /lib64/

You can install the 32 bit libraries on a 64 bit system - and things
will work.

Start with:
yum whatprovides "/lib/ld-linux.so"

-- 
Steven Haigh

Email: [log in to unmask]
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897



ATOM RSS1 RSS2