On Friday 19 January 2007 17:10, brullo nulla wrote: > > Dunno about gcc-4.2, you'll have to look at the gnu roadmap to get > > a hint of when they think it'll move closer to a release > > OK. > > > Not at all necessary. The kernel is a free standing block of C code > > and depends only on itself, so ABI issues with other apps simply > > don;t happen. As long as the kernel and all it's modules were > > compiled with the same compiler you will always be fine. (There are > > exceptions of course but with that rule of thumb you can't go > > wrong) > > Yes, but if I keep my 3.4.x compiled kernel and I recompile modules > in Portage with 4.1, there will be problems, maybe (for example, the > vmmon module of vmware-player). Well, I think I'll recompile. I have > other reasons to do it.
Hmmm, yes that's correct. emerge -e world will recompile vmware-modules, which will cause problems as you spotted. Kernel recompile is thus warranted > > Make sure any kernel modules you may have that are not in portage > > also get recompiled. > > Sure (I shouldn't have). I guess also programs not in portage will > have to be recompiled. Again, depends what they are. For example, I use e17 as my wm and while they technically do have ebuilds, they also might as well not be there for all the good they do. I can quite happily emerge -e world and not update e17 and everything still works, at least for that specific case. Other apps might be different. Professional audio stuff comes to mind, those apps often include drivers for fancy hardware that isn;t in the mainline trees, etc etc alan -- gentoo-user@gentoo.org mailing list
