VirtualBox

Ticket #6958 (closed defect: invalid)

Opened 4 years ago

Last modified 4 years ago

debian lenny - kernel compilation problem on self made kernel

Reported by: michele_petrazzo Owned by:
Priority: minor Component: installer
Version: VirtualBox 3.2.4 Keywords:
Cc: Guest type: other
Host type: Linux

Description

Hi all,
my system is a debian lenny with kernel compiled by myself (with bfs patch) and I found that there is a problem compiling vboxdrv (/etc/init.d/vboxdrv setup): error message (vbox-install.log) say me:
Makefile:170: * Error: /usr/src/linux (version 2.6.34) does not match the current kernel (version 2.6.34-bfs). Stop.

Looking around I see two things:

  • I have no /usr/src/linux link even if it's indicated
  • /lib/modules/2.6.34-bfs/build point to a directory (/home/michele/Download/kernel/linux-2.6.34) where I have the 2.6.34 kernel sources *with* bfs patch.

Conversely if I create the /build link pointing to /usr/src/linux-headers-2.6.34-bfs it compile without problem. So can be that Makefile look for the wrong file in case of self build kernels? (of course can be also a problem of the debian kernel installation / compile procedure, but I never seen other problems with other softwares, so... )

P.s. I compile the kernel with standard debian-way, so:
fakeroot make-kpkg --append-to-version -bfs kernel_image --initrd kernel_headers
dpkg -i linux-headers-2.6.34-bfs* linux-kernel-2-6.34-bfs*

Michele

Change History

comment:1 follow-up: ↓ 2 Changed 4 years ago by frank

  • Status changed from new to closed
  • Resolution set to invalid

No, your setup is wrong. The link /lib/modules/2.6.34-bfs/build is created by the corresponding linux-headers-2.6.34-bfs package.

Please check the following yourself:

make -sC /lib/modules/`uname -r`/build kernelrelease

must generate an output which is identical to

uname -r

If not (what I assume), then your setup is somehow wrong.

comment:2 in reply to: ↑ 1 Changed 4 years ago by michele_petrazzo

Replying to frank:

No, your setup is wrong. The link /lib/modules/2.6.34-bfs/build is created by the corresponding linux-headers-2.6.34-bfs package.

Just tried and no, the links (build and sources) aren't created by headers packages:
sudo dpkg -r linux-headers-2.6.34-bfs
sudo unlink source|build
sudo dpkg -i linux-headers-2.6.34-bfs_1_i386.deb

michele:~$ ll /lib/modules/2.6.34-bfs/ | grep sou
michele:~$ ll /lib/modules/2.6.34-bfs/ | grep build
michele:~$

Please check the following yourself:

make -sC /lib/modules/`uname -r`/build kernelrelease

must generate an output which is identical to

uname -r

With the right links yes, the output is identical ;)

If not (what I assume), then your setup is somehow wrong.

Since I don't create/touch or other anything else than fakeroot make-kpkg and dpkg -i and you are saying me that that links are wrong, I'll open a bug at debian.org

Thanks, Michele

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use