Should my Linux headers match my running kernel or what glibc was compiled against?
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
The last time I needed to deal with kernel headers was back in the Pleistocene (2.6 or so) and I remember back then that you needed to match your kernel headers not to the kernel you were running but to the kernel version glibc was compiled against. But this was a long time ago and before the kernel exported its own headers.
I have a computer that will be running a 4.15 series kernel, with a C library compiled against 4.4 series headers. Should I export the headers from the kernel I'm running, or use the headers package that my distro (Slackware) provides? (Or, and please say the answer is no, do I need to also rebuild glibc against the new kernel?)
linux-kernel glibc linux-headers
add a comment |Â
up vote
2
down vote
favorite
The last time I needed to deal with kernel headers was back in the Pleistocene (2.6 or so) and I remember back then that you needed to match your kernel headers not to the kernel you were running but to the kernel version glibc was compiled against. But this was a long time ago and before the kernel exported its own headers.
I have a computer that will be running a 4.15 series kernel, with a C library compiled against 4.4 series headers. Should I export the headers from the kernel I'm running, or use the headers package that my distro (Slackware) provides? (Or, and please say the answer is no, do I need to also rebuild glibc against the new kernel?)
linux-kernel glibc linux-headers
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
The last time I needed to deal with kernel headers was back in the Pleistocene (2.6 or so) and I remember back then that you needed to match your kernel headers not to the kernel you were running but to the kernel version glibc was compiled against. But this was a long time ago and before the kernel exported its own headers.
I have a computer that will be running a 4.15 series kernel, with a C library compiled against 4.4 series headers. Should I export the headers from the kernel I'm running, or use the headers package that my distro (Slackware) provides? (Or, and please say the answer is no, do I need to also rebuild glibc against the new kernel?)
linux-kernel glibc linux-headers
The last time I needed to deal with kernel headers was back in the Pleistocene (2.6 or so) and I remember back then that you needed to match your kernel headers not to the kernel you were running but to the kernel version glibc was compiled against. But this was a long time ago and before the kernel exported its own headers.
I have a computer that will be running a 4.15 series kernel, with a C library compiled against 4.4 series headers. Should I export the headers from the kernel I'm running, or use the headers package that my distro (Slackware) provides? (Or, and please say the answer is no, do I need to also rebuild glibc against the new kernel?)
linux-kernel glibc linux-headers
edited Feb 26 at 16:30
Jeff Schaller
31.2k846105
31.2k846105
asked Feb 26 at 16:25
Bandrami
593312
593312
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
I have an old Slackware server running a 4.6 kernel instead of its original 3.10 and have not had to mess with the headers. I've built at least a dozen kernels for half a dozen Slackware versions over the years and never did anything about headers or glibc on any of those.
Of course, without the newer headers, you may not be able to build software which uses features from that new kernel. But I doubt you'd be running Slackware if you wanted bleeding edge software so I don't think you'll run into that issue.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
I have an old Slackware server running a 4.6 kernel instead of its original 3.10 and have not had to mess with the headers. I've built at least a dozen kernels for half a dozen Slackware versions over the years and never did anything about headers or glibc on any of those.
Of course, without the newer headers, you may not be able to build software which uses features from that new kernel. But I doubt you'd be running Slackware if you wanted bleeding edge software so I don't think you'll run into that issue.
add a comment |Â
up vote
1
down vote
I have an old Slackware server running a 4.6 kernel instead of its original 3.10 and have not had to mess with the headers. I've built at least a dozen kernels for half a dozen Slackware versions over the years and never did anything about headers or glibc on any of those.
Of course, without the newer headers, you may not be able to build software which uses features from that new kernel. But I doubt you'd be running Slackware if you wanted bleeding edge software so I don't think you'll run into that issue.
add a comment |Â
up vote
1
down vote
up vote
1
down vote
I have an old Slackware server running a 4.6 kernel instead of its original 3.10 and have not had to mess with the headers. I've built at least a dozen kernels for half a dozen Slackware versions over the years and never did anything about headers or glibc on any of those.
Of course, without the newer headers, you may not be able to build software which uses features from that new kernel. But I doubt you'd be running Slackware if you wanted bleeding edge software so I don't think you'll run into that issue.
I have an old Slackware server running a 4.6 kernel instead of its original 3.10 and have not had to mess with the headers. I've built at least a dozen kernels for half a dozen Slackware versions over the years and never did anything about headers or glibc on any of those.
Of course, without the newer headers, you may not be able to build software which uses features from that new kernel. But I doubt you'd be running Slackware if you wanted bleeding edge software so I don't think you'll run into that issue.
answered Feb 26 at 17:27
Olivier
52127
52127
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f426727%2fshould-my-linux-headers-match-my-running-kernel-or-what-glibc-was-compiled-again%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password