Tracking dependency loop in kernel/kconfig












1















I'd like to track a dependency loop in the linux kernel kconfig setup.



When compiling with gcc-6.3 I can do the following without no issues:



$ make ARCH=powerpc custom_defconfig
$ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu-


However now if I try again with a gcc-8.2 release, it seems something new get's triggered. And instead I get:



$ make ARCH=powerpc custom_defconfig
$ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu-
GEN Makefile
scripts/kconfig/conf --syncconfig Kconfig
*
* Restart config...
*
*
* General architecture-dependent options
*
OProfile system profiling (OPROFILE) [M/n/y/?] m
Kprobes (KPROBES) [Y/n/?] y
Optimize very unlikely/likely branches (JUMP_LABEL) [N/y/?] n
Stack Protector buffer overflow detection (STACKPROTECTOR) [Y/n/?] (NEW)


I have of course verified my custom_defconfig is minimal (no diff against a savedefconfig run). So it seems I am triggering some kind of loop in the kconfig option. How do I track them, in order to report something accurate back to the kernel maintainers ?










share|improve this question





























    1















    I'd like to track a dependency loop in the linux kernel kconfig setup.



    When compiling with gcc-6.3 I can do the following without no issues:



    $ make ARCH=powerpc custom_defconfig
    $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu-


    However now if I try again with a gcc-8.2 release, it seems something new get's triggered. And instead I get:



    $ make ARCH=powerpc custom_defconfig
    $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu-
    GEN Makefile
    scripts/kconfig/conf --syncconfig Kconfig
    *
    * Restart config...
    *
    *
    * General architecture-dependent options
    *
    OProfile system profiling (OPROFILE) [M/n/y/?] m
    Kprobes (KPROBES) [Y/n/?] y
    Optimize very unlikely/likely branches (JUMP_LABEL) [N/y/?] n
    Stack Protector buffer overflow detection (STACKPROTECTOR) [Y/n/?] (NEW)


    I have of course verified my custom_defconfig is minimal (no diff against a savedefconfig run). So it seems I am triggering some kind of loop in the kconfig option. How do I track them, in order to report something accurate back to the kernel maintainers ?










    share|improve this question



























      1












      1








      1








      I'd like to track a dependency loop in the linux kernel kconfig setup.



      When compiling with gcc-6.3 I can do the following without no issues:



      $ make ARCH=powerpc custom_defconfig
      $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu-


      However now if I try again with a gcc-8.2 release, it seems something new get's triggered. And instead I get:



      $ make ARCH=powerpc custom_defconfig
      $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu-
      GEN Makefile
      scripts/kconfig/conf --syncconfig Kconfig
      *
      * Restart config...
      *
      *
      * General architecture-dependent options
      *
      OProfile system profiling (OPROFILE) [M/n/y/?] m
      Kprobes (KPROBES) [Y/n/?] y
      Optimize very unlikely/likely branches (JUMP_LABEL) [N/y/?] n
      Stack Protector buffer overflow detection (STACKPROTECTOR) [Y/n/?] (NEW)


      I have of course verified my custom_defconfig is minimal (no diff against a savedefconfig run). So it seems I am triggering some kind of loop in the kconfig option. How do I track them, in order to report something accurate back to the kernel maintainers ?










      share|improve this question
















      I'd like to track a dependency loop in the linux kernel kconfig setup.



      When compiling with gcc-6.3 I can do the following without no issues:



      $ make ARCH=powerpc custom_defconfig
      $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu-


      However now if I try again with a gcc-8.2 release, it seems something new get's triggered. And instead I get:



      $ make ARCH=powerpc custom_defconfig
      $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu-
      GEN Makefile
      scripts/kconfig/conf --syncconfig Kconfig
      *
      * Restart config...
      *
      *
      * General architecture-dependent options
      *
      OProfile system profiling (OPROFILE) [M/n/y/?] m
      Kprobes (KPROBES) [Y/n/?] y
      Optimize very unlikely/likely branches (JUMP_LABEL) [N/y/?] n
      Stack Protector buffer overflow detection (STACKPROTECTOR) [Y/n/?] (NEW)


      I have of course verified my custom_defconfig is minimal (no diff against a savedefconfig run). So it seems I am triggering some kind of loop in the kconfig option. How do I track them, in order to report something accurate back to the kernel maintainers ?







      linux linux-kernel make






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 15 at 7:32







      malat

















      asked Jan 14 at 20:54









      malatmalat

      539723




      539723






















          1 Answer
          1






          active

          oldest

          votes


















          1














          Turns out there was not dependency loop whatsoever, it was just a user error, the correct steps are to use the same compiler in the configuration and the build, eg:



          $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- custom_defconfig
          $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu-





          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',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            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%2f494495%2ftracking-dependency-loop-in-kernel-kconfig%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            Turns out there was not dependency loop whatsoever, it was just a user error, the correct steps are to use the same compiler in the configuration and the build, eg:



            $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- custom_defconfig
            $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu-





            share|improve this answer




























              1














              Turns out there was not dependency loop whatsoever, it was just a user error, the correct steps are to use the same compiler in the configuration and the build, eg:



              $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- custom_defconfig
              $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu-





              share|improve this answer


























                1












                1








                1







                Turns out there was not dependency loop whatsoever, it was just a user error, the correct steps are to use the same compiler in the configuration and the build, eg:



                $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- custom_defconfig
                $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu-





                share|improve this answer













                Turns out there was not dependency loop whatsoever, it was just a user error, the correct steps are to use the same compiler in the configuration and the build, eg:



                $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- custom_defconfig
                $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu-






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 16 at 7:52









                malatmalat

                539723




                539723






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494495%2ftracking-dependency-loop-in-kernel-kconfig%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    How to make a Squid Proxy server?

                    Is this a new Fibonacci Identity?

                    19世紀