The error message means the module also has compiled c-code which is probably stored in the directory VMware too. You might try one of the following:
a) If I understand you correctly, you had perl5.6.0 on the machine before you installed the other perl? If yes, the old installation should be still there. Perls of different versions can coexist on one machine.
Look into /usr/lib/perl5/5.6.0. If there are files, your old libraries are still there. Look into /usr/bin/. Is there still a file perl5.6.0 in there, everything is still in place, you are just using the wrong perl. In that case 'rm /usr/local/bin/perl' (you can still use this new version with '/usr/local/bin/perl5.8.0' after this).
Make sure /usr/bin/perl is the exact same size as /usr/bin/perl5.6.0, otherwise do 'rm /usr/bin/perl; ln /usr/bin/perl5.6.0 /usr/bin/perl'. Everything should work again
b) If you never had perl5.6.0 on the machine you might copy it from one of the other vmwares:
Copy all the files in /usr/lib/perl5 recursively (for example using 'scp -rp')
Then copy the following files from /usr/bin: perl5.6.0
perl
xsubpp
splain
shasum
s2p
ptardiff
ptar
pstruct
psed
podselect
podchecker
pod2usage
pod2text
pod2man
pod2latex
pod2html
pl2pm
piconv
perlivp
perldoc
perlbug
libnetcfg
instmodsh
h2xs
h2ph
find2perl
enc2xs
dprofpp
cpanp-run-perl
cpanp
cpan2dist
c2ph
a2p
imgsize
ysh
. If you don't have some of them on the source machine, no problem, I made that list from my perl10.0 installation, there might have been changes between these versions. The most important file is 'perl', you might not need most or all of the rest for the operation of the vmware scripts.
If the machine you are copying from is similar enough to the target machine (i.e. obviously you can't use a sparc or powerpc machine to copy to a x86 machine since there are executables involved) this should work now.
|