On Wed, 2006-08-09 at 12:52 -0400, Justin Denick wrote: > Wow, that's weird you would tell me that I don't, because I had to do > it today.
Yet, you didn't file a bug. > And oh wow, it happened to this guy too. > It happened here > http://www.lxnaydesign.net/forum/viewtopic.php?t=753&sid=fd67540a6eb10f7200700a600608ad76 RR4/RR64. I don't think I really need to say much more. They make modifications to lots of things, so any reports from them are likely bunk. It also doesn't help that the posts in question prove almost no information. > What's that? the actual vmware website has a post about it. ...with almost no real information to actually see that the problem is very likely a specific local problem that could probably be worked around in a much different manner. Again, there's no bug report on it, so who knows. > Holy smokes Batman!!! Yes, your amazing wit baffles even the Caped Crusader. > http://www.vmware.com/community/message.jspa?messageID=370107 > > I searched the list archives and seen no sign of this so i added one. > If you are not affected than by it than all the better for you. Twice > I have installed the vmware-workstation and each time I have had to > link the afore mentioned file. Perhaps, if you took a few moments to try to file a bug report and actually get something like this resolved, if it is actually a bug, rather than responding with pointless retorts, it would make the situation better. The funny thing is, as I have said, there are exactly 0 bug reports on this. I, personally, run over 40 VMware Workstation installations, using everything from GCC 3.3 to GCC 4.1.1. I also maintain VMware Workstation, and have heard *nothing* about this, not even from the people using the experimental overlay, and there have been *hundreds* of people using it. While I am not saying that there is not a bug affecting your system, I *am* saying that your *requirement* to get VMware Workstation running is nothing of the sort. Please file a bug report on this and we can determine the *real* cause of the problem, as well as determine a proper solution. Either that, or you can just continue with your witty bantor, and I can just ignore the whole thing, since nobody else seems to be experiencing it or consider it important enough to file a bug. > On 8/9/06, Chris Gianelloni <[EMAIL PROTECTED]> wrote: > On Wed, 2006-08-09 at 10:31 -0400, Justin Denick wrote: > > When upgrading or installing Vmware you must remove or > rename the > > file: > > /opt/vmware/workstation/lib/lib/libgcc_s.so.1/libgcc_s.so.1 > > and then copy or link the > > file /usr/lib/gcc/iXXX-pc-linux-gnu/X.X.X/libgcc_s.so.1 > > the the /opt/vmware/workstation/lib/lib/libgcc_s.so.1/ > directory. > > Umm... no you don't. I have about 40 VMware installations to > prove it. > -- Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
