bad ELF interpreter: No such file or directory

[WildRice]

I installed the RedHat Linux tarball on an AMD 64 FC3 machine. This machine is x86_64 only, there are no i386 RPMs installed.

 

Running Install.sh gives me:

 

# sh ./Install.sh

 

Install Retrospect Client? (y/n): y

./Install.sh: /usr/local/dantz/client/retroclient: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory

 

Adding RETROSPECT_HOME to system profile and login scripts...Done!

 

Before attempting to use any of the GUI components of the Retrospect Client,

you must have both the RETROSPECT_HOME and DISPLAY variables set. The

RETROSPECT_HOME variable should point to /usr/local/dantz/client. We have

modified your /etc/profile and /etc/.login files to set this value for future

logins. The retrospect client launched as part of this installation process

will also have this variable set. However, if you kill that client and

restart it without logging out, you will need to set these variables manually.

 

Starting client as daemon...

/usr/local/dantz/client/rcl: /usr/local/dantz/client/retroclient: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory

 

Installation was successful, but Retrospect Client for Linux could not

be started. If this is an upgrade, please wait 5 minutes, then start

the client manually by running $ /usr/local/dantz/client/rcl start

Your system appears to be compatible with the startup system used

by Red Hat and S.u.S.E. Would you like to create symbolic links

to automatically start Retrospect Client for Linux? (y/n): y

 

 

 

 

What do I need to do to get this client working? -Chuck-

[WildRice]

 

No answer.

 

Does Dantz not read the Fourms?

Surely I am not the only one that has Linux systems on their network?

-Chuck-

[queball]

Perhaps you should post your Linux message in the Linux client forum.

 

I'm guessing one answer you should expect to receive is that the client is not currently supported on a 64 bit platform.