Should my Linux headers match my running kernel or what glibc was compiled against?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
2
down vote

favorite
1












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?)







share|improve this question


























    up vote
    2
    down vote

    favorite
    1












    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?)







    share|improve this question
























      up vote
      2
      down vote

      favorite
      1









      up vote
      2
      down vote

      favorite
      1






      1





      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?)







      share|improve this question














      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?)









      share|improve this question













      share|improve this question




      share|improve this question








      edited Feb 26 at 16:30









      Jeff Schaller

      31.2k846105




      31.2k846105










      asked Feb 26 at 16:25









      Bandrami

      593312




      593312




















          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.






          share|improve this answer




















            Your Answer







            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "106"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            convertImagesToLinks: false,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );








             

            draft saved


            draft discarded


















            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






























            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.






            share|improve this answer
























              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.






              share|improve this answer






















                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.






                share|improve this answer












                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.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Feb 26 at 17:27









                Olivier

                52127




                52127






















                     

                    draft saved


                    draft discarded


























                     


                    draft saved


                    draft discarded














                    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













































































                    Popular posts from this blog

                    How to check contact read email or not when send email to Individual?

                    Bahrain

                    Postfix configuration issue with fips on centos 7; mailgun relay