(Buildroot) “silentoldconfig” error on compile












0














I just moved an old buildroot folder from an old VM to a newer one to consolidate. I thought that simply moving the folder, along with any dependent folders, and making the appropriate path/name changes would be all that is required to get it up and running in the new VM.



Unfortunately, this appears to not be the case as I am greeted with the following error upon attempting to build in this new VM:



#
# configuration written to /home/mirion/mirion/buildroot-2013.05/.config
#
/usr/bin/make -j5 HOSTCC="/usr/bin/gcc" HOSTCXX="/usr/bin/g++" silentoldconfig
make[1]: Entering directory '/home/mirion/mirion/buildroot-2013.05'
BR2_DEFCONFIG='' KCONFIG_AUTOCONFIG=/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/auto.conf KCONFIG_AUTOHEADER=/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/autoconf.h KCONFIG_TRISTATE=/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/tristate.config BUILDROOT_CONFIG=/home/mirion/mirion/buildroot-2013.05/.config /home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/conf --silentoldconfig Config.in

*** Error during update of the configuration.

Makefile:692: recipe for target 'silentoldconfig' failed
make[1]: *** [silentoldconfig] Error 1
make[1]: Leaving directory '/home/mirion/mirion/buildroot-2013.05'
Makefile:396: recipe for target '/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/auto.conf' failed
make: *** [/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/auto.conf] Error 2
mv: cannot stat 'output/images/rootfs.ubi': No such file or directory


Are there any ideas as to what I can do to resolve this?



I did some poking around on google but could not find anything conclusive.



EDIT: Original VM was running Lubuntu 12.04, the new VM is running Ubuntu 17.10.



Thanks.










share|improve this question





























    0














    I just moved an old buildroot folder from an old VM to a newer one to consolidate. I thought that simply moving the folder, along with any dependent folders, and making the appropriate path/name changes would be all that is required to get it up and running in the new VM.



    Unfortunately, this appears to not be the case as I am greeted with the following error upon attempting to build in this new VM:



    #
    # configuration written to /home/mirion/mirion/buildroot-2013.05/.config
    #
    /usr/bin/make -j5 HOSTCC="/usr/bin/gcc" HOSTCXX="/usr/bin/g++" silentoldconfig
    make[1]: Entering directory '/home/mirion/mirion/buildroot-2013.05'
    BR2_DEFCONFIG='' KCONFIG_AUTOCONFIG=/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/auto.conf KCONFIG_AUTOHEADER=/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/autoconf.h KCONFIG_TRISTATE=/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/tristate.config BUILDROOT_CONFIG=/home/mirion/mirion/buildroot-2013.05/.config /home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/conf --silentoldconfig Config.in

    *** Error during update of the configuration.

    Makefile:692: recipe for target 'silentoldconfig' failed
    make[1]: *** [silentoldconfig] Error 1
    make[1]: Leaving directory '/home/mirion/mirion/buildroot-2013.05'
    Makefile:396: recipe for target '/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/auto.conf' failed
    make: *** [/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/auto.conf] Error 2
    mv: cannot stat 'output/images/rootfs.ubi': No such file or directory


    Are there any ideas as to what I can do to resolve this?



    I did some poking around on google but could not find anything conclusive.



    EDIT: Original VM was running Lubuntu 12.04, the new VM is running Ubuntu 17.10.



    Thanks.










    share|improve this question



























      0












      0








      0







      I just moved an old buildroot folder from an old VM to a newer one to consolidate. I thought that simply moving the folder, along with any dependent folders, and making the appropriate path/name changes would be all that is required to get it up and running in the new VM.



      Unfortunately, this appears to not be the case as I am greeted with the following error upon attempting to build in this new VM:



      #
      # configuration written to /home/mirion/mirion/buildroot-2013.05/.config
      #
      /usr/bin/make -j5 HOSTCC="/usr/bin/gcc" HOSTCXX="/usr/bin/g++" silentoldconfig
      make[1]: Entering directory '/home/mirion/mirion/buildroot-2013.05'
      BR2_DEFCONFIG='' KCONFIG_AUTOCONFIG=/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/auto.conf KCONFIG_AUTOHEADER=/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/autoconf.h KCONFIG_TRISTATE=/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/tristate.config BUILDROOT_CONFIG=/home/mirion/mirion/buildroot-2013.05/.config /home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/conf --silentoldconfig Config.in

      *** Error during update of the configuration.

      Makefile:692: recipe for target 'silentoldconfig' failed
      make[1]: *** [silentoldconfig] Error 1
      make[1]: Leaving directory '/home/mirion/mirion/buildroot-2013.05'
      Makefile:396: recipe for target '/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/auto.conf' failed
      make: *** [/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/auto.conf] Error 2
      mv: cannot stat 'output/images/rootfs.ubi': No such file or directory


      Are there any ideas as to what I can do to resolve this?



      I did some poking around on google but could not find anything conclusive.



      EDIT: Original VM was running Lubuntu 12.04, the new VM is running Ubuntu 17.10.



      Thanks.










      share|improve this question















      I just moved an old buildroot folder from an old VM to a newer one to consolidate. I thought that simply moving the folder, along with any dependent folders, and making the appropriate path/name changes would be all that is required to get it up and running in the new VM.



      Unfortunately, this appears to not be the case as I am greeted with the following error upon attempting to build in this new VM:



      #
      # configuration written to /home/mirion/mirion/buildroot-2013.05/.config
      #
      /usr/bin/make -j5 HOSTCC="/usr/bin/gcc" HOSTCXX="/usr/bin/g++" silentoldconfig
      make[1]: Entering directory '/home/mirion/mirion/buildroot-2013.05'
      BR2_DEFCONFIG='' KCONFIG_AUTOCONFIG=/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/auto.conf KCONFIG_AUTOHEADER=/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/autoconf.h KCONFIG_TRISTATE=/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/tristate.config BUILDROOT_CONFIG=/home/mirion/mirion/buildroot-2013.05/.config /home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/conf --silentoldconfig Config.in

      *** Error during update of the configuration.

      Makefile:692: recipe for target 'silentoldconfig' failed
      make[1]: *** [silentoldconfig] Error 1
      make[1]: Leaving directory '/home/mirion/mirion/buildroot-2013.05'
      Makefile:396: recipe for target '/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/auto.conf' failed
      make: *** [/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/auto.conf] Error 2
      mv: cannot stat 'output/images/rootfs.ubi': No such file or directory


      Are there any ideas as to what I can do to resolve this?



      I did some poking around on google but could not find anything conclusive.



      EDIT: Original VM was running Lubuntu 12.04, the new VM is running Ubuntu 17.10.



      Thanks.







      ubuntu compiling configuration cross-compilation buildroot






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Apr 9 '18 at 18:06







      lukemk1

















      asked Apr 9 '18 at 17:57









      lukemk1lukemk1

      246




      246






















          1 Answer
          1






          active

          oldest

          votes


















          0














          I switched to using "olddefconfig" instead, it seems to work.






          share|improve this answer








          New contributor




          Alastair is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.


















            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%2f436584%2fbuildroot-silentoldconfig-error-on-compile%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









            0














            I switched to using "olddefconfig" instead, it seems to work.






            share|improve this answer








            New contributor




            Alastair is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.























              0














              I switched to using "olddefconfig" instead, it seems to work.






              share|improve this answer








              New contributor




              Alastair is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.





















                0












                0








                0






                I switched to using "olddefconfig" instead, it seems to work.






                share|improve this answer








                New contributor




                Alastair is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                I switched to using "olddefconfig" instead, it seems to work.







                share|improve this answer








                New contributor




                Alastair is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                share|improve this answer



                share|improve this answer






                New contributor




                Alastair is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                answered 19 mins ago









                AlastairAlastair

                1




                1




                New contributor




                Alastair is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.





                New contributor





                Alastair is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






                Alastair is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






























                    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.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • 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%2f436584%2fbuildroot-silentoldconfig-error-on-compile%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

                    CARDNET

                    Boot-repair Failure: Unable to locate package grub-common:i386

                    濃尾地震