On Sat, 29 Jan 2011, David wrote: > On 1/29/2011 1:53 PM, Robert P. J. Day wrote: > > On Sat, 29 Jan 2011, David wrote: > > > >> On 1/29/2011 8:36 AM, Robert P. J. Day wrote: > >>> On Sat, 29 Jan 2011, Richard Shaw wrote: > >>> > >>>> On Sat, Jan 29, 2011 at 7:02 AM, Robert P. J. Day > >>>> <[email protected]> wrote: > >>>>> > >>>>> followup to my earlier post, there's this: > >>>>> > >>>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/579813 > >>>>> > >>>>> since i'm running a bleeding-edge kernel, vbox 4.0.2 won't build on my > >>>>> ubuntu system as it's looking for that header file in its old > >>>>> location. thoughts? > >>>> > >>>> Well, outside of fixing the code yourself (assuming you were running > >>>> the OSE version) have you tried a symbolic to the old location to > >>>> make it happy? > >>> > >>> of course that's an obvious fix, but it doesn't address the larger > >>> issue of expecting *everyone* to be able to realize what's happened, > >>> and manually make the same fix. i would think that the simpler > >>> solution would be to tweak the vbox source to simply add that > >>> generated/ directory to the include search path, so it will build for > >>> both older and newer kernels. > >> > >> > >> In the past VirtualBox has not 'chased betas and alphas'. My guess here > >> would be that when or if this kernel change is actually in a supported > >> distribution release this will be corrected. > > > > this is not "chasing" alphas or betas -- that change of location > > goes back to dec of 2009: > > > > https://patchwork.kernel.org/patch/69431/ > > > > why it's never been an issue until now is a mystery. > > > I see. That I did not know. Is this kernel, or any of the others > with this shift, actually in any distribution?
the thing is, this change appears to go back to the 2.6.33 kernel. here's the git commit for this: commit 5a865c0606eb44d5d12cabb429751c83712183de Merge: 331d9d5 46e75f6 Author: Linus Torvalds <[email protected]> Date: Thu Dec 17 07:23:42 2009 -0800 Merge branch 'for-33' of git://repo.or.cz/linux-kbuild * 'for-33' of git://repo.or.cz/linux-kbuild: (29 commits) net: fix for utsrelease.h moving to generated gen_init_cpio: fixed fwrite warning kbuild: fix make clean after mismerge kbuild: generate modules.builtin genksyms: properly consider EXPORT_UNUSED_SYMBOL{,_GPL}() score: add asm/asm-offsets.h wrapper unifdef: update to upstream revision 1.190 kbuild: specify absolute paths for cscope kbuild: create include/generated in silentoldconfig scripts/package: deb-pkg: use fakeroot if available scripts/package: add KBUILD_PKG_ROOTCMD variable scripts/package: tar-pkg: use tar --owner=root Kbuild: clean up marker net: add net_tstamp.h to headers_install kbuild: move utsrelease.h to include/generated kbuild: move autoconf.h to include/generated <--- THERE drop explicit include of autoconf.h kbuild: move compile.h to include/generated kbuild: drop include/asm kbuild: do not check for include/asm-$ARCH ... snip ... so i'm puzzled why i never noticed this before. but clearly anything which counts on finding autoconf.h in the old location isn't going to work anymore. or maybe i'm just confused. oh, and i tried to install vmware player on the same system, and i got an error with that as well, and it appears to have the same cause. so i'm open to explanations. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
