It seems app-emulation/emul-linux-x86-baselibs-1.1 broke my vmware. Fixing my problem only requires downgrading to emul-linux-x86-baselibs-1.0. Portage 2.0.50-r6 (default-amd64-2004.0, gcc-3.3.3, glibc-2.3.3_pre20040207-r0, 2.6.5-gentoo-r1) ================================================================= System uname: 2.6.5-gentoo-r1 x86_64 4 Gentoo Base System version 1.4.10 Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CFLAGS="-O2" CHOST="x86_64-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo ftp://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://vlaai.snt.ipv6.utwente.nl/pub/os/linux/gentoo/ ftp://mirrors.tds.net/gentoo http://ftp.du.se/pub/os/gentoo http://ftp6.uni-erlangen.de/pub/mirrors/gentoo ftp://gentoo.chem.wisc.edu/gentoo/ ftp://ftp.ipv6.uni-muenster.de/pub/linux/distributions/gentoo ftp://gentoo.mirrors.pair.com/ ftp://vlaai.snt.ipv6.utwente.nl/pub/os/linux/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/bmg/portage /home/core/Data/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aac aalib acl acpi alsa amd64 apache2 apm arts audiofile avi berkdb breakme cddb cdr chroot clamav crypt curl dv dvd dvdr encode escreen esd etwin evms2 evo faad fam fax fbcon flac flash foomaticdb gdbm gif gimpprint glut gnome gpm gstreamer gtk gtk2 icq imagemagick imap imlib imlib2 ipv6 irda jabber jack java javascript jpeg kde libg++ libgda libwww lirc mad maildir matroska mcal menu mikmod mng mono motif mozilla mpeg mpeg4 msn mysql ncurses nls nntp nogcj nvidia offensive ofx oggvorbis opengl oscar oss pam parse-clocks pcap pdflib perl physfs pic png ppds psyco pwdb python qt quicktime readline rplay samba sasl sdl slang snmp socks5 sox speex spell ssl stroke tcltk tcpd theora tiff transcode truetype usb wmf wxwindows xml2 xmms xv xvid yahoo zlib"
What's the breakage you mean ? Does it crash using emul-linux....-1.1 ? Or doesn't it start at all ? Please provide the error message as well as the version of vmware you are using and the md5sum of the emul-linux-x86-baselibs-1.1.ebuild. (md5sum /usr/portage/app-emulation/emul-linux-x86-baselibs/emul-linux-x86-baselibs-1.1.ebuild)
I guess there is no error. Just *poof*. vmware-workstation-4.5.1.7568 5a6f8865e339320acec47c35a9fbd1e2 /usr/portage/app-emulation/emul-linux-x86-baselibs/emul-linux-x86-baselibs-1.1.ebuild
I should read more carefully. vmware will start, but will not power-on any VM. It gets just about ready to POST, and then nothing.
There is a reason why vmware is not keyworded for amd64, not just because I hadn't gotten around to it. Should I explicitly add -amd64 to the keywords to try to make this point more clear?
Hey, just trying to be a good citizen and put something out there so others can see. I have it working, so others might want to know how, and searching bugzilla is one good way to do it. Just mark it "WONTFIX" and be a good sport. I'll just try and keep up with /etc/portage/package.mask.
I didn't mean for that to come across as rude as it read. I'm asking seriously, do I need to implicitly add -amd64 to vmware so people will understand that it is a known broken configuration and that we do not support it?
Maybe, but what may be better would be some verbosity in the ebuild's text about brokenness, and maybe even bug numbers. Thanks for your attention. I realise how third party brokenness can be frustrating. I work for a software firm. Has anyone spoken with Petr Vandrovec <petr@vandrovec.name> about a little helping hand? Maybe if some budget was carved out to buy him an amd64 barebones. I think he lacks hardware to properly support the any-any updates for amd64.
Personally, I feel it would be much better suited to ask VMWare to support the platform than to have some third party do so, especially in the areas which are not directly the result of the kernel modules. The problems which are rampant in VMWare are much more low-level than I think could be fixed with a patch or two. I have updated the VMWare ebuild to state that amd64 is not a supported platform and that the user should check out the recent bugs (with numbers) for more information. Hopefully, this will solve many of the bugs coming in for vmware and amd64, and may even get VMWare moving quicker (go bug them, not us... ;p) on supporting amd64.
64-bit will be supported soon: http://www.vmware.com/news/releases/64bit.html
Yeah... their sales group has me on their mailing list now... ;]
