|
From: Vahis on 4 Jul 2008 13:49 More strange issues after updating 10.3 to 11.0: Your kernel was built with "gcc" version "4.3.1", while you are trying to use "/usr/bin/gcc" version "4.3". This configuration is not recommended and VMware Server may crash if you'll continue. Please try to use exactly same compiler as one used for building your kernel. Now what? Vahis -- Training new things here: http://waxborg.servepics.com "The only thing more expensive than training is the lack of it" Henry Ford
From: Markus Kossmann on 4 Jul 2008 14:23 Vahis wrote: > More strange issues after updating 10.3 to 11.0: > > Your kernel was built with "gcc" version "4.3.1", while you are trying > to use "/usr/bin/gcc" version "4.3". > This configuration is not recommended and VMware Server may crash if > you'll continue. Please try to use exactly same compiler as > one used for building your kernel. > > Now what? Ignore it. The vmware build scripts use "gcc -dumpversion" to get the compiler version, where they should use the last line of "gcc -v"
From: Vahis on 4 Jul 2008 15:13 On 2008-07-04, Markus Kossmann <mkossmann_n1(a)gmx.de> wrote: > Vahis wrote: > >> More strange issues after updating 10.3 to 11.0: >> >> Your kernel was built with "gcc" version "4.3.1", while you are trying >> to use "/usr/bin/gcc" version "4.3". >> This configuration is not recommended and VMware Server may crash if >> you'll continue. Please try to use exactly same compiler as >> one used for building your kernel. >> >> Now what? > Ignore it. The vmware build scripts use "gcc -dumpversion" to get the > compiler version, where they should use the last line of "gcc -v" Thanks for that info. I'm not too good with scripts. I ran the script wihout any probs. I'm not sure if I've seen this message before, although the script needs to be run after each kernel or vmware change. Anyway, it worked :) Vahis -- Training new things here: http://waxborg.servepics.com "The only thing more expensive than training is the lack of it" Henry Ford
From: houghi on 4 Jul 2008 15:12 Vahis wrote: > More strange issues after updating 10.3 to 11.0: <snip> > Now what? With all the things that are happening, how about a new install? houghi -- This space left blank intentionaly
From: Vahis on 4 Jul 2008 16:15 On 2008-07-04, houghi <houghi(a)houghi.org.invalid> wrote: > Vahis wrote: >> More strange issues after updating 10.3 to 11.0: ><snip> >> Now what? > > With all the things that are happening, how about a new install? It's OK now technically. That meaning that the upgrade as such was successful. But there's not much gain in it. Faster zypper is good. That's the only gain I've seen so far. KDE 4 is useless, I'm back to 3. Firefox 3 is not to my liking, but I'll try it out for some time. This has nothing to do with Suse though. And I can put FF 2 back and keep it if needed, no biggie. My two faves are YaST and Konqueror. YaST has got better and Konqueror I'm still able to keep as it is. But it looks like it's going to a direction I don't fancy too much. And the Nautilus thingy is out of question. So when I put all together, I won't even consider a fresh install. Maybe I'll go back to 10.3 which is just a boot away. I don't really see the point in 11.0 I ran 10.0 since day one through the whole of its life. I skipped 10.1 (that was a bad one) after trying pretty hard. I skipped 10.2 (obviously not as bad) after not much effort. Luckily 10.3 was there when 10.0 got obsolete. I've run it since day one. I like it. I'm pretty sure there will be another pearl like it before it dies. 11.0 is not very important to me. Vahis -- Training new things here: http://waxborg.servepics.com "The only thing more expensive than training is the lack of it" Henry Ford
|
Next
|
Last
Pages: 1 2 Prev: Where is Apache2-mod_rewrite in 11.0? Next: S3 Unichrome Pro 11.0 gets it wrong everytime! |