virtualbox, vmware and generated/autoconf.h in the kernel source tree

[Robert P. J. Day]

  not really a ubuntu issue but i tripped over both of these issues
this morning on my ubuntu system so i'll pass it on.

  since i like to roll my own kernels and stay up to date with the
main kernel git repo, i'm currently running:

$ uname -r
2.6.38-rc2-00274-g1f0324c-dirty
$

which works fine, except that this now breaks the installation of both
virtualbox and vmware.  that's because (based on what i read) the
location of the generated autoconf.h file when you build a recent
kernel from source has *moved*, from <linux/autoconf.h> to
<generated/autoconf.h>.

  that won't have any effect on simply *running* that kernel, but it
will certainly cause havoc with any software you install that, say,
needs to build any kernel modules and goes looking for the autoconf.h
file in its old location.  you can read about that here:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/579813

just thought i'd mention this in case anyone else trips over it.

rday

-- 

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================