[SOLVED] Updated to kernel 3.0.4 but now source package can not find kernel headers.
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Updated to kernel 3.0.4 but now source package can not find kernel headers.
This started yesterday after updating my kernel to version 3.0.4. This part of Linux is where I usually have issues heavily when I do custom kernels.
After updating my kernel and redoing my symlinks, to the source and all now when I compile a package that looks for the kernel headers it stated they can not be found.
I've tried working around this editing the files that generate errors to manually probe to the direct path of the kernel headers, example:
Where as a package use to have:
I've hasd to edit it to include the full path:
Due to this issue package that are SlackBuilds can not compile unless I do a manual audit of the package to relink the headers as the compiler generate errors one file at a time. I've even had to do this to several kernel headers as well.
Is there anything I can do to restore the kernel headers to a functional state so I don't have to perform a manual audit and edit of all the files as errors are generated?
When you compile the kernel yourself you'll just have to worry with the resulting image (bzImage), the .config and System.map files, only. You'll _NOT_ touch any headers nor firmware (although this last one will _mostly_ give you no problem if you install them). The reason you should not touch any headers is that they must be the ones which glibc was compiled with (the kernel-headers package distributed by Slackware). No, there's no problem running a kernel 3.0.4 with the headers from 220.127.116.11. A good explanation about this is at Alien Bob's wiki about compiling your own kernel - http://alien.slackbook.org/dokuwiki/...kernelbuilding