I hate installing these fixes that come from 'somewhere'. I know that this guy had the fix when udev didn't work with vmware (I never needed it, however, because I figured out that the stop script was missing from rc.d/init.6, and also that udev could be make to learn about the vmnet* devices). So... I guess it's probably ok. Now he has the gcc fix. Thanks for the help. Have just downloaded it. *** Wonder how much longer vmware 4.5 will run on fedora anyway. Knowing the lifetime of commercial software, nice as it is, it was likely a waste of money. I only use vmware to run Corel Photo Paint (and Draw sometimes). Gimp is such a nuisance, with all those windows that open up and you can never get it to do much. On 4/13/05, Robert Locke <lists@xxxxxxxxx> wrote: > On Wed, 2005-04-13 at 19:38 -0600, kwhiskers wrote: > > Just did an update of the kernel and everything went smoothly, as > > always. Have the nvidia driver directly from nvidia. Very reliable. > > > > But then I noticed that KNemo was showing my vmnet1 and vmnet8 icons > > greyed out. No problem, had forgotten to run the vmware-config.pl > > script. Ran it, was told the new kernel was compiled with gcc 3.4.3 > > and I have 3.4.2. Sure enough, after doing an update of the system, > > the new gcc-3.4.3 arrived. > > > > Well, tried to reconfigure vmware using the proper gcc, and I get this error: > > > <snip> > > > > Any ideas? The new kernel was compiled with a gcc that is not the one > > that has been released? So, where do I get the right gcc? > > > > Just dealt with this earlier this morning. You now have the right gcc, > but apparently some things changed in some header files with the new > kernel. > > I downloaded the latest vmware update from: > > http://platan.vc.cvut.cz/ftp/pub/vmware/vmware-any-any-update90.tar.gz > > Once I installed that, the compile went smooth..... > > --Rob > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list >
