You are not logged in.
Pages: 1
I just finished compiling Kernel 2.6.38.2 and intend on installing virtualbox. I see that it requires kernel26-headers as a dependency. My question is in two parts: One, am I correct in assuming that the headers in the repos are for the kernel in the repos (2.6.37 I think)? Two, if I am correct in the previous assumption, do I need to compile headers for my new kernel and how would I do that. Note that I did not use a PKGBUILD for the installation, I followed the instructions here with the "traditional method". Thanks.
Regards, Michael Smith
Offline
1) Yes. You need headers that match the installed kernel.
2) Don't use the traditional method. Use ABS to build kernel26 renaming it or use my kernel26-ck package and modify it with the included nconfig option. Link in my sig.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
I enjoy using the traditional method. As far as I can tell, there aren't any advantages to the ABS method (if there are, other than unification through pacman, by all means tell me). But my question is left unanswered: How would I go about compiling the headers for 2.6.38.2?
Regards, Michael Smith
Offline
At the core of Arch is pacman... if you wish do it manually, you'll need to see the PKGBUILD and replicate the headers package in the shell... why in the world you would want to do that is beyond me.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Thank you. I guess trying the abs method wouldn't hurt. My main issue was configuration. I've only just skimmed the PKGBUILD so I'm not aware of how it handles it. I suppose I could write my own as described in the wiki as well. Thanks again.
Edit: Further research has revealed to me that the kernel headers are merely there for when the full source tree isn't. Seeing as the full tree is present in my case, the headers are unnecessary. I may take graysky's advice though and use pacman to manage my kernel.
Last edited by smithr.michael1997 (2011-03-31 02:17:29)
Regards, Michael Smith
Offline
guy ,maybe you should to do this:
change to your kernel directory invoke the the following commads
make mrproper
make headers_check
make INSTALL_HDR_PATH=dest headers_install
copy dest/include/* to your header-file directory
Offline
Pages: 1