When running vmware-config.pl: Unknown VMware Workstation 6.0.0 build 45731 detected. Building for Workstation 5.5.3. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config1/vmmon-only' make -C /lib/modules/2.6.20-gentoo-r8-tcn/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-2.6.20-gentoo-r8' When lookin at /tmp/vmare-config0/.../getversion.pl I notice that the file from Nov 12 06 and indeed doesn't know VMWare 6 yet. # qlist -Iv|grep -i vmware app-emulation/vmware-modules-1.0.0.16-r1 app-emulation/vmware-workstation-6.0.0.45731 Reproducible: Always
That's correct, You appear to be using the a vmware-config.pl that isn't installed by the vmware-modules/vmware-workstation ebuilds. The vmware-workstation ebuilds should be patching your vmware-config.pl so that it doesn't compile the modules (since they're compiled by vmware-modules). It looks from your error as though it's using the vmware-any-any-update ebuild (which doesn't yet know about workstation-6). Could you please state whether any of these ebuilds are from the vmware overlay, and can you please also say whether you ran 'vmware-config.pl' or '/opt/vmware/workstation/bin/vmware-config.pl'? Thanks 5:)
Yes, it's appling the any-any patch. # emerge vmware-workstation Calculating dependencies... done! >>> Verifying ebuild Manifests... >>> Emerging (1 of 1) app-emulation/vmware-workstation-6.0.0.45731 to / * vmware-any-any-update109.tar.gz MD5 ;-) ... [ ok ] * vmware-any-any-update109.tar.gz RMD160 ;-) ... [ ok ] * vmware-any-any-update109.tar.gz SHA1 ;-) ... [ ok ] * vmware-any-any-update109.tar.gz SHA256 ;-) ... [ ok ] * vmware-any-any-update109.tar.gz size ;-) ... [ ok ] * VMware-workstation-6.0.0-45731.x86_64.tar.gz MD5 ;-) ... [ ok ] * VMware-workstation-6.0.0-45731.x86_64.tar.gz RMD160 ;-) ... [ ok ] * VMware-workstation-6.0.0-45731.x86_64.tar.gz SHA1 ;-) ... [ ok ] * VMware-workstation-6.0.0-45731.x86_64.tar.gz SHA256 ;-) ... [ ok ] * VMware-workstation-6.0.0-45731.x86_64.tar.gz size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking VMware-workstation-6.0.0-45731.x86_64.tar.gz ;-) ... [ ok ] * checking vmware-any-any-update109.tar.gz ;-) ... No, I don't use the vmware overlay and I ran `vmware-config.pl`. BTW on amd64 vmware-modules needs the i386 archive while vmware-workstation needs the x86_64 one: /usr/portage/distfiles/VMware-workstation-6.0.0-45731.i386.tar.gz /usr/portage/distfiles/VMware-workstation-6.0.0-45731.x86_64.tar.gz (one is actually a symlink to the other :)
Thanks for that information. Please could you try running /opt/vmware/workstation/bin/vmware-config.pl instead of just vmware-config.pl. Please also check whether `which vmware-config.pl` is a symlink to /opt/vmware/... or if it's a file in it's own right. I have the feeling you've got some left-over files from a previous installation which are incorrectly attempting to manually compile the modules...
# which vmware-config.pl /opt/vmware/workstation/bin/vmware-config.pl Well, I deleted this file, re-emerge vmware-workstation and ran /opt/vmware/workstation/bin/vmware-config.pl - still same misbehaviour :-\ But this is actually not a surprise since the any-any patch is being applied...
Well, it is pretty odd, since patch /usr/portage/app-emulation/vmware-workstation/files/6.0.0.45731/004_all_do-not-build-modules.patch, should be being applied, and should stop vmware-config.pl from attempting to do anything with the modules. Could you please include the bit right after the list of files, that says which patches are actually applied? Also please attach the full output from a run of vmware-config.pl. Thanks 5:)
uninitialized value...funny :) i attached the complete output of emerge and vmware-config. # vmware-config.pl --help VMware Workstation 6.0.0 build-45731 for Linux configurator Usage: /opt/vmware/workstation/bin/vmware-config.pl [[-][-]d[efault]] [[-][-]c[ompile]] [[-][-]p[rebuilt]] [[-][-]t[ry-modules]][[-][-]e[xperimental]] . default: Automatically answer questions with the proposed answer. . compile: Force the compilation of kernel modules. . prebuilt: Force the use of pre-built kernel modules. . try-modules: Try to load all the compatible modules from the VMware Workstation package.. experimental: Prompt for configuration of any experimental features. Use of uninitialized value in addition (+) at /opt/vmware/workstation/bin/vmware-config.pl line 1018. Command line arguments: The acceptable characters are: the letters A, B, C, ..., the letters a, b, c, ..., the numbers 0, 1, 2, ..., and the special characters '_' and '-' and '='.
Created attachment 124240 [details] emerge vmware-workstation
Created attachment 124241 [details] vmware-config.pl
Ok, that means there's something up with your portage tree, since it should be applying several patches, and you should be seeing something like the following: >>> Unpacking source... >>> Unpacking VMware-workstation-6.0.0-45731.i386.tar.gz to /var/tmp/portage/app-emulation/vmware-workstation-6.0.0.45731/work >>> Unpacking vmware-any-any-update109.tar.gz to /var/tmp/portage/app-emulation/vmware-workstation-6.0.0.45731/work * Fallback PaX marking -m scanelf: Nothing to scan !? * Applying various patches (bugfixes/updates) ... * 000_all_initd-location.patch ... [ ok ] * 001_all_fix-permissions.patch ... [ ok ] * 002_all_pagebreak-detection-fix.patch ... [ ok ] * 004_all_do-not-build-modules.patch ... [ ok ] * 007_all_use-modprobe-over-insmod.patch ... [ ok ] * 009_all_init.d-modules-warning.patch ... [ ok ] * Done with patching >>> Source unpacked. >>> Compiling source in /var/tmp/portage/app-emulation/vmware-workstation-6.0.0.45731/work/vmware-distrib ... >>> Source compiled. Can you please include your emerge --info so that we can check you don't have any unusual RSYNC options, or overlays that may be causing problems. Also, please check that you have files in /usr/portage/app-emulation/vmware-workstation/files/6.0.0.45731. Hopefully we'll get to the bottom of this soon... 5:)
ls -l /usr/portage/app-emulation/vmware-workstation/files/6.0.0.45731/ total 24 -rw-r--r-- 1 root root 1133 Jun 24 21:32 000_all_initd-location.patch -rw-r--r-- 1 root root 647 Jun 24 21:32 001_all_fix-permissions.patch -rw-r--r-- 1 root root 800 Jun 24 21:32 002_all_pagebreak-detection-fix.patch -rw-r--r-- 1 root root 654 Jun 24 21:32 004_all_do-not-build-modules.patch -rw-r--r-- 1 root root 448 Jun 24 21:32 007_all_use-modprobe-over-insmod.patch -rw-r--r-- 1 root root 991 Jun 24 21:32 009_all_init.d-modules-warning.patch emerge --info attached
Created attachment 124245 [details] emerge --info
Thanks, It looks as though you've got all the required files, so all I can imagine is that the ebuild isn't being emerged from the portage directory, but from some other directory. Your /usr/local/portage overlay might be the cause of the problem. Could you please try running: emerge --sync && PORTDIR_OVERLAY="" emerge -1 =vmware-workstation-6.0.0.45731 That should ensure that you're not using any modified files, and that you haven't put some of the required files in an overlay and not all of them. It'll make sure the ebuild from the portage dir is used and that no old vmware eclass files are present. Please check to see whether the patches are applied (as in comment 9) and if they are, check whether the configuration works successfully. If not, then we'll have to go back to the drawing board... 5:)
Hmm, there's a lot different now. Apparently something was terribly messed up... Everything seems to work now...except vmware: $ vmware /opt/vmware/workstation/lib/bin/vmware: symbol lookup error: /opt/vmware/workstation/lib/lib/libvmwareui.so.0/libvmwareui.so.0: undefined symbol: _ZThn24_N4view10FieldEntry17delete_text_vfuncEii BTW and I don't need the i386 tar no more as well...
Uh, and I'd to download the tar from vmware.com again because the size was suddently wrong.
I'm glad we found the solution. My suggestion is to check your /usr/local/portage directory for eclasses and other vmware related ebuilds. As to the missing symbol, I'd try recompiling libview, libsexy, libsexymm and also gtkmm. Hopefully that will fix your vmware running problems. In the meantime, I'm going to mark this bug as fixed...
