LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
Reload this Page [SOLVED] Can't Build VirtualBox Kernel Module in 13.1
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 04-26-2011, 06:35 PM   #1
Woodsman
Senior Member
 
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482

Rep: Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546
Can't Build VirtualBox Kernel Module in 13.1

Edit: First part of this post is solved. See my second post for an explanation. I still can't build 3.2.12 on 12.2 (second half of this post).

I am using the 13.1 build scripts from slackbuilds.org. I modified the scripts to build 3.2.12 rather than 3.2.10.

In 13.1 the main VirtualBox 3.2.12 OSE package built and installed without errors. The VirtualBox GUI starts without errors.

Running the virtualbox-kernel-mksrctarball.sh script built a kernel source package without errors.

Yet the VirtualBox kernel module won't build. I receive the following error:

Code:
]*** Building 'vboxdrv' module ***
make[1]: Entering directory `/dev/shm/virtualbox-kernel-3.2.12/vboxdrv'
make KBUILD_VERBOSE= -C /lib/modules/2.6.33.11-smp-2/build SUBDIRS=/dev/shm/virtualbox-kernel-3.2.12/vboxdrv SRCROOT=/dev/shm/virtualbox-kernel-3.2.12/vboxdrv modules
make[2]: Entering directory `/home/public/builds/kernels/linux-2.6.33.11-smp'
  CC [M]  /dev/shm/virtualbox-kernel-3.2.12/vboxdrv/linux/SUPDrv-linux.o
/bin/sh: scripts/basic/fixdep: Permission denied
make[3]: *** [/dev/shm/virtualbox-kernel-3.2.12/vboxdrv/linux/SUPDrv-linux.o] Error 1
make[2]: *** [_module_/dev/shm/virtualbox-kernel-3.2.12/vboxdrv] Error 2
make[2]: Leaving directory `/home/public/builds/kernels/linux-2.6.33.11-smp'
make[1]: *** [vboxdrv] Error 2
make[1]: Leaving directory `/dev/shm/virtualbox-kernel-3.2.12/vboxdrv'
make: *** [all] Error 2
As far as I can tell, /home/public/builds/kernels/linux-2.6.33.11-smp/scripts/basic/fixdep is not a shell script.

I obtain the same results when trying to build the 3.2.10 kernel module.

In 13.1 I am using the 2.6.33.11 smp kernel.

I use a separate build location for my package builds. I built the 2.6.3.11 smp kernel from /home/public/builds/kernels/linux-2.6.33.11-smp.

I'm aware there is an installation script available from Oracle. I want to stick with the SlackBuild and OSE version.

I'm aware there are newer versions, but I prefer 3.2.12.

Any ideas?

Edit:

Seems I also can't build 3.2.12 on 12.2:

Code:
  CXX     VBoxBFE - {C}/src/VBox/Frontends/VBoxBFE/KeyboardImpl.cpp
  CXX     VBoxBFE - {C}/src/VBox/Frontends/VBoxBFE/StatusImpl.cpp
  CXX     VBoxBFE - {C}/src/VBox/Frontends/VBoxBFE/MachineDebuggerImpl.cpp
  CXX     VBoxBFE - {C}/src/VBox/Frontends/VBoxBFE/VMControl.cpp
  CXX     VBoxBFE - {C}/src/VBox/Frontends/VBoxBFE/HGCM.cpp
  CXX     VBoxBFE - {C}/src/VBox/Frontends/VBoxBFE/HGCMThread.cpp
  CXX     VBoxBFE - {C}/src/VBox/Frontends/VBoxBFE/HGCMObjects.cpp
  bin2c   VBoxBFE - {C}/src/VBox/Frontends/VBoxBFE/ico64x01.pnm
  CXX     VBoxBFE - {C}/src/VBox/Frontends/VBoxBFE/SDLFramebuffer.cpp
  CXX     VBoxHeadless - {C}/src/VBox/Frontends/VBoxHeadless/VBoxHeadless.cpp
  CXX     VBoxHeadless - {C}/src/VBox/Frontends/VBoxHeadless/FramebufferVNC.cpp
  GEN     {T}/VirtualBox_stripped.xidl
The failing command:
@g++ -c -O2 -g -pipe -pedantic -Wshadow -Wall -Wextra -Wno-missing-field-initializers -Wno-unused -Wno-trigraphs -fdiagnostics-show-option -Wno-long-long -Wno-variadic-macros -Wno-long-long -Wno-non-virtual-dtor -Wshadow -fshort-wchar -fpermissive -fexceptions -frtti -march=i586 -O2 -mtune=generic -fno-omit-frame-pointer -fno-strict-aliasing -fvisibility-inlines-hidden -fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT  -pthread -m32 -I/dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release/bin/sdk/bindings/xpcom/include -I/dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release/bin/sdk/bindings/xpcom/include/xpcom -I/dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release/bin/sdk/bindings/xpcom/include/string -I/dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release/bin/sdk/bindings/xpcom/include/xpcom -I/dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release/bin/sdk/bindings/xpcom/include/nsprpub -I/dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release/bin/sdk/bindings/xpcom/include/ipcd -I/dev/shm/VirtualBox-3.2.12_OSE/include -I/dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release -DRTPATH_APP_PRIVATE=\"/usr/share/virtualbox\" -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\"/usr/share/virtualbox\" -DRTPATH_APP_PRIVATE_ARCH=\"/usr/lib/virtualbox\" -DRTPATH_SHARED_LIBS=\"/usr/lib/virtualbox\" -DRTPATH_APP_DOCS=\"\" -DRTPATH_APP_PRIVATE=\"/usr/share/virtualbox\" -DRT_OS_LINUX -D_FILE_OFFSET_BITS=64 -DRT_ARCH_X86 -D__X86__ -DIN_RING3 -DUNICODE -DNDEBUG=1 -DVBOX_WITH_XPCOM -DVBOX_WITH_XPCOM_NAMESPACE_CLEANUP -DNDEBUG -DTRIMMED -DVBOX_FFMPEG -DVBOX_WITH_GUEST_PROPS -DVBOX_WITH_VNC -Wp,-MD,/dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release/obj/VBoxHeadless/FramebufferVNC.o.dep -Wp,-MT,/dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release/obj/VBoxHeadless/FramebufferVNC.o -Wp,-MP -o /dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release/obj/VBoxHeadless/FramebufferVNC.o /dev/shm/VirtualBox-3.2.12_OSE/src/VBox/Frontends/VBoxHeadless/FramebufferVNC.cpp
The failing command:
@g++ -c -O2 -g -pipe -pedantic -Wshadow -Wall -Wextra -Wno-missing-field-initializers -Wno-unused -Wno-trigraphs -fdiagnostics-show-option -Wno-long-long -Wno-variadic-macros -Wno-long-long -Wno-non-virtual-dtor -Wshadow -fshort-wchar -fpermissive -fexceptions -frtti -march=i586 -O2 -mtune=generic -fno-omit-frame-pointer -fno-strict-aliasing -fvisibility-inlines-hidden -fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT  -pthread -m32 -I/dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release/bin/sdk/bindings/xpcom/include -I/dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release/bin/sdk/bindings/xpcom/include/xpcom -I/dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release/bin/sdk/bindings/xpcom/include/string -I/dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release/bin/sdk/bindings/xpcom/include/xpcom -I/dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release/bin/sdk/bindings/xpcom/include/nsprpub -I/dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release/bin/sdk/bindings/xpcom/include/ipcd -I/dev/shm/VirtualBox-3.2.12_OSE/include -I/dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release -DRTPATH_APP_PRIVATE=\"/usr/share/virtualbox\" -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\"/usr/share/virtualbox\" -DRTPATH_APP_PRIVATE_ARCH=\"/usr/lib/virtualbox\" -DRTPATH_SHARED_LIBS=\"/usr/lib/virtualbox\" -DRTPATH_APP_DOCS=\"\" -DRTPATH_APP_PRIVATE=\"/usr/share/virtualbox\" -DRT_OS_LINUX -D_FILE_OFFSET_BITS=64 -DRT_ARCH_X86 -D__X86__ -DIN_RING3 -DUNICODE -DNDEBUG=1 -DVBOX_WITH_XPCOM -DVBOX_WITH_XPCOM_NAMESPACE_CLEANUP -DNDEBUG -DTRIMMED -DVBOX_FFMPEG -DVBOX_WITH_GUEST_PROPS -DVBOX_WITH_VNC -Wp,-MD,/dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release/obj/VBoxHeadless/VBoxHeadless.o.dep -Wp,-MT,/dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release/obj/VBoxHeadless/VBoxHeadless.o -Wp,-MP -o /dev/shm/VirtualBox-3.2.12_OSE/out/linux.x86/release/obj/VBoxHeadless/VBoxHeadless.o /dev/shm/VirtualBox-3.2.12_OSE/src/VBox/Frontends/VBoxHeadless/VBoxHeadless.cpp
kmk[2]: Leaving directory `/dev/shm/VirtualBox-3.2.12_OSE'
kmk[2]: Entering directory `/dev/shm/VirtualBox-3.2.12_OSE'
kmk[1]: Leaving directory `/dev/shm/VirtualBox-3.2.12_OSE'
Last edited by Woodsman; 04-26-2011 at 09:29 PM.
 
Old 04-26-2011, 09:27 PM   #2
Woodsman
Senior Member
 
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482

Original Poster
Rep: Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546
Original problem solved. None of the scripts in the kernel build location were executable. I might have done that inadvertently doing some house keeping.

However, I would like to solve the problem with building on 12.2 too. I need to maintain 12.2 and I'd like to update VirtualBox. Preferably with the same version used in 13.1 (and eventually 13.37) as I want to share the same virtual machines between the two systems. Any help is appreciated.
Last edited by Woodsman; 04-26-2011 at 09:29 PM.
 
Old 04-26-2011, 10:52 PM   #3
Woodsman
Senior Member
 
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482

Original Poster
Rep: Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546
Solved
The problem with building on 12.2 was in the LocalConfig.kmk configuration. The build directive VBOX_WITH_VNC was set to true, but I had no VNC libraries installed. Taking a cue from 13.1, I built and installed libvncserver on 12.2. I then finally got past the error.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] VirtualBox & The New 2.6.37.3 Kernel. (Solution: DKMS Required To Install VB Kernel Module) cwizardone Slackware 49 03-17-2011 06:42 PM
[SOLVED] VirtualBox < 3.1.4 module build fails on 2.6.33 kernel rpedrica Slackware 12 03-29-2010 07:23 AM
[Error] Kernel Module : No kernel module build environment saman007uk Debian 7 09-09-2006 06:34 PM
LXer: Howto: build Linux kernel module against installed kernel w/o full kernel source tree LXer Syndicated Linux News 0 09-03-2006 08:21 PM
Unable to build NVIDIA kernel module / determin kernel version Night Ink Fedora 2 05-31-2004 04:54 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:45 PM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration