Summary: | app-emulation/virtualbox-modules-1.6.6-r1 fails to compile on kernel 2.6.29 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marco Wirz <marco.wirz> |
Component: | Current packages | Assignee: | Markus Ullmann (RETIRED) <jokey> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | andy.dalton, dvitas, d_ion, gentoo, gothic0000, heavymetal, JakesAddress, joachim.herb, p-twohig, patrick, patrizio.bassi, peter_sliepenbeek, sebastian.treu, skelter |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 267267 | ||
Bug Blocks: | |||
Attachments: |
paths that solves the compilation error
This ebuild applies the patch and compiles cleanly New ebuild for kernels >= 2.6.29 (see comment #11) |
Description
Marco Wirz
2009-04-24 09:23:02 UTC
1.6 is oooooold. 2.1.4 will be stable soon enough, so we'll just wait (see bug 267267 ) and then close this one, eh? :) Well, as far as I can see, despite being old it is still the latest stable version. But now the case is documented, in case someone else finds this problem. Maybe somebody could post the correct fix for the ebuild here. I just modified the condition in the if clause to if kernel_is 2 6 29 ; then since I don't know the correct solution. (I assume there are people here who need as much as a couple of seconds for that. I don't belong to this group :-) The patch itself applies fine, so only the condition has to be modified. For all those less experienced gentoo users: You have to do "ebuild virtualbox-modules-1.6.6-r1.ebuild digest" after modifying the ebuid file. If there will be a newer stable version soon, I'm fine with sitting it out. Created attachment 190346 [details] paths that solves the compilation error Ported from patch provided in: http://bugs.gentoo.org/256809 Created attachment 190348 [details] This ebuild applies the patch and compiles cleanly Ported from ebuild provided in: http://bugs.gentoo.org/256809 After updating to gentoo-source 2.6.29r5 I am also getting the error messages about missing euid and egid when building app-emulation/virtualbox-modules-1.6.6-r1. Please integrate this patch! *** Bug 272965 has been marked as a duplicate of this bug. *** this also applies to the 2.6.30 kernel I am one of those inexperienced users (at least concerning patching ebuilds) and did not succeed in patching the build of virtualbox-modules-1.6.6-r1 in order to run on gentoo 2.6.29. Can anyone point me to proper directions for patching the ebuild? Or better yet, incorporate the patches in gentoo and issue an intermediate patch virtualbox-modules-1.6.6-r2! (In reply to comment #8) > I am one of those inexperienced users (at least concerning patching ebuilds) > and did not succeed in patching the build of virtualbox-modules-1.6.6-r1 in > order to run on gentoo 2.6.29. > > Can anyone point me to proper directions for patching the ebuild? Or better > yet, incorporate the patches in gentoo and issue an intermediate patch > virtualbox-modules-1.6.6-r2! > 1. Download the ebuild attachment and replace it with the old ebuild 2. Download the patch and save it under 'files' directory naming it depending on your kernel. 3. issue: ebuild /usr/portage/app-emulation/virtualbox-modules/virtualbox-modules-1.6.6-r1.ebuild manifest. 4. Emerge the package. Regards, (In reply to comment #9) > (In reply to comment #8) > > I am one of those inexperienced users (at least concerning patching ebuilds) > > and did not succeed in patching the build of virtualbox-modules-1.6.6-r1 in > > order to run on gentoo 2.6.29. > > > > Can anyone point me to proper directions for patching the ebuild? Or better > > yet, incorporate the patches in gentoo and issue an intermediate patch > > virtualbox-modules-1.6.6-r2! > > > > 1. Download the ebuild attachment and replace it with the old ebuild > 2. Download the patch and save it under 'files' directory naming it depending > on your kernel. > 3. issue: ebuild > /usr/portage/app-emulation/virtualbox-modules/virtualbox-modules-1.6.6-r1.ebuild > manifest. > 4. Emerge the package. > > Regards, > This steps work for me on 2.6.30-gentoo-r4, thanks! (In reply to comment #1) > 1.6 is oooooold. 2.1.4 will be stable soon enough, so we'll just wait (see bug > 267267 ) and then close this one, eh? :) Not to be impatient, but the latest stable virtualbox-modules + the latest stable kernel has been busted for four mounths now. :-) Having a app-emulation/virtualbox-modules-1.6.6-r2 that could handle all kernel versions >= 2.6.29 in the tree would be a tremendous help until one of the newer versions does eventually become stable. Maybe changing if kernel_is 2 6 29 to if kernel_is ge 2 6 29 in the attached ebuild would do the trick? Thanks for your help! The patch also works for me. Also I'd say integrate with portage asap, it's just a super super harmless patch. After several months vbox is still broken.. (In reply to comment #10) > (In reply to comment #9) > > (In reply to comment #8) > > > I am one of those inexperienced users (at least concerning patching ebuilds) > > > and did not succeed in patching the build of virtualbox-modules-1.6.6-r1 in > > > order to run on gentoo 2.6.29. > > > > > > Can anyone point me to proper directions for patching the ebuild? Or better > > > yet, incorporate the patches in gentoo and issue an intermediate patch > > > virtualbox-modules-1.6.6-r2! > > > > > > > 1. Download the ebuild attachment and replace it with the old ebuild > > 2. Download the patch and save it under 'files' directory naming it depending > > on your kernel. > > 3. issue: ebuild > > /usr/portage/app-emulation/virtualbox-modules/virtualbox-modules-1.6.6-r1.ebuild > > manifest. > > 4. Emerge the package. > > > > Regards, > > > > This steps work for me on 2.6.30-gentoo-r4, thanks! > This also worked for me on 2.6.30-r4 . Please admins, add this fix to the main branch. *** Bug 283350 has been marked as a duplicate of this bug. *** Created attachment 203105 [details] New ebuild for kernels >= 2.6.29 (see comment #11) Applied the change from Comment #11 to the ebuild. Tested and works fine for me on 2.6.30-gentoo-r4 amd64. Please, add to portage or mark 1.6.6 unstable, right now this is NOT a stable package! (In reply to comment #15) > Created an attachment (id=203105) [edit] > New ebuild for kernels >= 2.6.29 (see comment #11) > > Applied the change from Comment #11 to the ebuild. > Tested and works fine for me on 2.6.30-gentoo-r4 amd64. > > Please, add to portage or mark 1.6.6 unstable, right now this is NOT a stable > package! > Doesn't works here, on x86 2.6.30-gentoo-r4 But an error seems different this time. ... i686-pc-linux-gnu-gcc -Wp,-MD,/var/tmp/portage/app-emulation/virtualbox-modules-1.6.6-r3/work/vboxdrv/r0drv/linux/.initterm-r0drv-linux.o.d -nostdinc -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.3.2/include -Iinclude -I/usr/src/linux-2.6.30-gentoo-r4/arch/x86/include -include include/linux/autoconf.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -fno-delete-null-pointer-checks -Os -m32 -msoft-float -mregparm=3 -freg-struct-return -mpreferred-stack-boundary=2 -march=k8 -Wa,-mtune=generic32 -ffreestanding -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -fno-stack-protector -fomit-frame-pointer -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -I/usr/src/linux/include -I/var/tmp/portage/app-emulation/virtualbox-modules-1.6.6-r3/work/vboxdrv/ -I/var/tmp/portage/app-emulation/virtualbox-modules-1.6.6-r3/work/vboxdrv/include -I/var/tmp/portage/app-emulation/virtualbox-modules-1.6.6-r3/work/vboxdrv/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DCONFIG_VBOXDRV_AS_MISC -DRT_ARCH_X86 -DUSE_NEW_OS_INTERFACE_FOR_MM -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(initterm_r0drv_linux)" -D"KBUILD_MODNAME=KBUILD_STR(vboxdrv)" -c -o /var/tmp/portage/app-emulation/virtualbox-modules-1.6.6-r3/work/vboxdrv/r0drv/linux/initterm-r0drv-linux.o /var/tmp/portage/app-emulation/virtualbox-modules-1.6.6-r3/work/vboxdrv/r0drv/linux/initterm-r0drv-linux.c /var/tmp/portage/app-emulation/virtualbox-modules-1.6.6-r3/work/vboxdrv/r0drv/linux/alloc-r0drv-linux.c: In function ‘rtMemAlloc’: /var/tmp/portage/app-emulation/virtualbox-modules-1.6.6-r3/work/vboxdrv/r0drv/linux/alloc-r0drv-linux.c:138: error: ‘_PAGE_KERNEL_EXEC’ undeclared (first use in this function) /var/tmp/portage/app-emulation/virtualbox-modules-1.6.6-r3/work/vboxdrv/r0drv/linux/alloc-r0drv-linux.c:138: error: (Each undeclared identifier is reported only once /var/tmp/portage/app-emulation/virtualbox-modules-1.6.6-r3/work/vboxdrv/r0drv/linux/alloc-r0drv-linux.c:138: error: for each function it appears in.) make[2]: *** [/var/tmp/portage/app-emulation/virtualbox-modules-1.6.6-r3/work/vboxdrv/r0drv/linux/alloc-r0drv-linux.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[1]: *** [_module_/var/tmp/portage/app-emulation/virtualbox-modules-1.6.6-r3/work/vboxdrv] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.30-gentoo-r4' make: *** [vboxdrv] Error 2 Patch along with -r3 ebuild works for me at 2.6.30-gentoo-r5 amd64 any chance to have these patches in portage? 3.0 stable everywhere. |