Matthew thank you for your very clear and understandable explanation.
This gutsy install has /lib32, /lib64, /usr/lib32 and /usr/lib64. Adept
has a package named ia32-libs which I installed, ran vmware-config.pl
once again, and the installation proceeded without error, vmware starts
as expected.
So in summary, there were 3 things I needed to do: install
build-essential, xinetd, and ia32-libs first (Adept or apt-get install),
then install vmware-server.
Thanks to everyone who has replied.
Cheers,
Roger
Matthew Gregan wrote:
At 2007-11-07T09:16:16+1300, Roger Searle wrote:
Issues are that these libraries are actually on the system, it is just
that VMWare doesn't seem to be able to know where they are, the hacks
suggested
I'll be more explicit this time.
Ignore the "invalid key" errors for now. The install script is confused and
reporting the wrong problem. The script is trying to run vmware utilities,
but they are failing because they cannot start due to missing libraries.
Once you fix the library problem, the "invalid key" errors will disappear.
On Linux with platforms where the 64-bit CPU is backwards compatible with
32-bit code, there are two types of distributions available: pure 64-bit,
and multi-architecture. Most distros ship multi-architecture, which means
they ship both 32-bit and 64-bit code (install in separate directories), but
they usually only install the bare minimum 32-bit.
Depending on the distro, you may find the 64-bit libraries in /lib64 and
/usr/lib64 and the 32-bit libraries in /lib and /usr/lib or the 32-bit
libraries in /lib32 and /usr/lib32 and the 64-bit libraries in /lib and
/usr/lib.
In this case, you have x86-64 (64-bit) versions of the same libraries
installed, but the vmware binary you are using is i386 (32-bit)--the 64-bit
libraries are not compatible with it. You need to:
- Find out if there is a 64-bit version of the vmware binary available (not
sure if there is, suspect not since there's no great need for it).
OR
- Install the 32-bit versions of the required libraries from your distro's
repository. The details on how to do this differs between distributions.
For Ubuntu, it looks like they ship a small set of 32-bit libraries in a
single package (ia32-libs), and then others are available as lib32<name>,
e.g. lib32z1 for a 32-bit libz.so.
Cheers,
-mjg
