My system got "screw" due to running from the linux source code: make headers_install which installed headers not compatible or not working with, for example parted.

My question is: How does Slackware pack kernel-headers?!

If someone knows, please let me know

Thx!

Please see here.

1 members found this post helpful.

That does not answer my question... I need to know how Slackware created kernel-headers package.

I suggest you ask such a question in the Slackware forum, you will receive more relevant answers.

AFAIK the kernel-headers package is (probably one of the only ones if not the only one) created by hand by Patrick Volkerding. Installing the package put in /usr/include some files and directories copied from the kernel source tree then does this :
That's about all.

To check which files are involved just do this for instance:
Then compare the files in the newly created usr directory to those included in the linux-26.33.4 kernel source tree.

Some posts of this thread could be of interest to you as well

[EDIT] To fix your kernel headers (I suppose you use Slackware-13.0, otherwise adapt accordingly):
You can reinstall kernel-source the same way, of course.

Why did you do that ?.

Because Im testing and there is not where written how to generate your own kernel-headers.

Hmmm - why did you think you needed to do that ?.
See the reference in post #2 - are you rebuilding glibc ?. And you'd better have a real good reason if your answer is "yes".

1 members found this post helpful.

I dont wanna rebuild glibc, I wanna create kernel-headers package...

'nuff said - goodbye.

Why?

glibc and the kernel-headers are two packages joined at the hip. You should never upgrade one without upgrading the other.

If you do this, your system will malfunction.

My advice is to reinstall the stock kernel-headers package, and not upgrade it until you upgrade glibc.

A new kernel does not need new kernel-headers.

My guess is robertjinx wants to do that just for fun, no need to argue against that

Plenty of reason to argue against that for any non source distro.
Rebuilding the tool-chain in a distro designed to handle it is a PITA. Else you'd better have a substantial reason to attempt it - and don't bleat when you don't understand when it causes problems with the rest of the environment.

No sympathy here.

Moved to Slackware (not a Programming question)

I once had the same question, 'till I read the reference on the second link. Once you read it, one can simply understand that create a kernel-headers package is no good for anything - you'll just copy the headers and then package them; you can't install them since glibc depends on the distribuited kernel-headers package. If you can't install them nor do anything with them, why bother to create a kernel-headers package?

...Unless, of course, you're building glibc. That's another story.