Yocto Bitbake Glibc build fails





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I'm trying to build a Yocto image but the build fails when compiling glibc.



If I run just



bitbake glibc -c compile


I get a compilation error as follows:



/usr/src/debug/glibc/2.27-r0/git/nptl/pthread_atfork.c:51: undefined reference to `__dso_handle'
| /media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi.gcc-cross-initial-arm/../../libexec/arm-poky-linux-gnueabi.gcc-cross-initial-arm/gcc/arm-poky-linux-gnueabi/7.3.0/ld: /media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/build-arm-poky-linux-gnueabi/rt/librt.so: hidden symbol `__dso_handle' isn't defined
| /media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi.gcc-cross-initial-arm/../../libexec/arm-poky-linux-gnueabi.gcc-cross-initial-arm/gcc/arm-poky-linux-gnueabi/7.3.0/ld: final link failed: Bad value
| collect2: error: ld returned 1 exit status
| ../Makerules:599: recipe for target '/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/build-arm-poky-linux-gnueabi/rt/librt.so' failed
| make[2]: *** [/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/build-arm-poky-linux-gnueabi/rt/librt.so] Error 1
| make[2]: Leaving directory '/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/git/rt'
| Makefile:235: recipe for target 'rt/others' failed
| make[1]: *** [rt/others] Error 2
| make[1]: Leaving directory '/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/git'
| Makefile:9: recipe for target 'all' failed
| make: *** [all] Error 2
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/temp/log.do_compile.31096)
ERROR: Task (/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/meta/recipes-core/glibc/glibc_2.27.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 227 tasks of which 226 didn't need to be rerun and 1 failed.


The glibc library is obviously very important so how can I resolved the compilation error?










share|improve this question































    0















    I'm trying to build a Yocto image but the build fails when compiling glibc.



    If I run just



    bitbake glibc -c compile


    I get a compilation error as follows:



    /usr/src/debug/glibc/2.27-r0/git/nptl/pthread_atfork.c:51: undefined reference to `__dso_handle'
    | /media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi.gcc-cross-initial-arm/../../libexec/arm-poky-linux-gnueabi.gcc-cross-initial-arm/gcc/arm-poky-linux-gnueabi/7.3.0/ld: /media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/build-arm-poky-linux-gnueabi/rt/librt.so: hidden symbol `__dso_handle' isn't defined
    | /media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi.gcc-cross-initial-arm/../../libexec/arm-poky-linux-gnueabi.gcc-cross-initial-arm/gcc/arm-poky-linux-gnueabi/7.3.0/ld: final link failed: Bad value
    | collect2: error: ld returned 1 exit status
    | ../Makerules:599: recipe for target '/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/build-arm-poky-linux-gnueabi/rt/librt.so' failed
    | make[2]: *** [/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/build-arm-poky-linux-gnueabi/rt/librt.so] Error 1
    | make[2]: Leaving directory '/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/git/rt'
    | Makefile:235: recipe for target 'rt/others' failed
    | make[1]: *** [rt/others] Error 2
    | make[1]: Leaving directory '/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/git'
    | Makefile:9: recipe for target 'all' failed
    | make: *** [all] Error 2
    | ERROR: oe_runmake failed
    | WARNING: exit code 1 from a shell command.
    | ERROR: Function failed: do_compile (log file is located at /media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/temp/log.do_compile.31096)
    ERROR: Task (/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/meta/recipes-core/glibc/glibc_2.27.bb:do_compile) failed with exit code '1'
    NOTE: Tasks Summary: Attempted 227 tasks of which 226 didn't need to be rerun and 1 failed.


    The glibc library is obviously very important so how can I resolved the compilation error?










    share|improve this question



























      0












      0








      0








      I'm trying to build a Yocto image but the build fails when compiling glibc.



      If I run just



      bitbake glibc -c compile


      I get a compilation error as follows:



      /usr/src/debug/glibc/2.27-r0/git/nptl/pthread_atfork.c:51: undefined reference to `__dso_handle'
      | /media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi.gcc-cross-initial-arm/../../libexec/arm-poky-linux-gnueabi.gcc-cross-initial-arm/gcc/arm-poky-linux-gnueabi/7.3.0/ld: /media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/build-arm-poky-linux-gnueabi/rt/librt.so: hidden symbol `__dso_handle' isn't defined
      | /media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi.gcc-cross-initial-arm/../../libexec/arm-poky-linux-gnueabi.gcc-cross-initial-arm/gcc/arm-poky-linux-gnueabi/7.3.0/ld: final link failed: Bad value
      | collect2: error: ld returned 1 exit status
      | ../Makerules:599: recipe for target '/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/build-arm-poky-linux-gnueabi/rt/librt.so' failed
      | make[2]: *** [/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/build-arm-poky-linux-gnueabi/rt/librt.so] Error 1
      | make[2]: Leaving directory '/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/git/rt'
      | Makefile:235: recipe for target 'rt/others' failed
      | make[1]: *** [rt/others] Error 2
      | make[1]: Leaving directory '/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/git'
      | Makefile:9: recipe for target 'all' failed
      | make: *** [all] Error 2
      | ERROR: oe_runmake failed
      | WARNING: exit code 1 from a shell command.
      | ERROR: Function failed: do_compile (log file is located at /media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/temp/log.do_compile.31096)
      ERROR: Task (/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/meta/recipes-core/glibc/glibc_2.27.bb:do_compile) failed with exit code '1'
      NOTE: Tasks Summary: Attempted 227 tasks of which 226 didn't need to be rerun and 1 failed.


      The glibc library is obviously very important so how can I resolved the compilation error?










      share|improve this question
















      I'm trying to build a Yocto image but the build fails when compiling glibc.



      If I run just



      bitbake glibc -c compile


      I get a compilation error as follows:



      /usr/src/debug/glibc/2.27-r0/git/nptl/pthread_atfork.c:51: undefined reference to `__dso_handle'
      | /media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi.gcc-cross-initial-arm/../../libexec/arm-poky-linux-gnueabi.gcc-cross-initial-arm/gcc/arm-poky-linux-gnueabi/7.3.0/ld: /media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/build-arm-poky-linux-gnueabi/rt/librt.so: hidden symbol `__dso_handle' isn't defined
      | /media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi.gcc-cross-initial-arm/../../libexec/arm-poky-linux-gnueabi.gcc-cross-initial-arm/gcc/arm-poky-linux-gnueabi/7.3.0/ld: final link failed: Bad value
      | collect2: error: ld returned 1 exit status
      | ../Makerules:599: recipe for target '/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/build-arm-poky-linux-gnueabi/rt/librt.so' failed
      | make[2]: *** [/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/build-arm-poky-linux-gnueabi/rt/librt.so] Error 1
      | make[2]: Leaving directory '/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/git/rt'
      | Makefile:235: recipe for target 'rt/others' failed
      | make[1]: *** [rt/others] Error 2
      | make[1]: Leaving directory '/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/git'
      | Makefile:9: recipe for target 'all' failed
      | make: *** [all] Error 2
      | ERROR: oe_runmake failed
      | WARNING: exit code 1 from a shell command.
      | ERROR: Function failed: do_compile (log file is located at /media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/build-microchip/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/glibc/2.27-r0/temp/log.do_compile.31096)
      ERROR: Task (/media/g/01D476BE2E4F26B0/AT91/SAMA5D27_SOM1/yocto/poky/meta/recipes-core/glibc/glibc_2.27.bb:do_compile) failed with exit code '1'
      NOTE: Tasks Summary: Attempted 227 tasks of which 226 didn't need to be rerun and 1 failed.


      The glibc library is obviously very important so how can I resolved the compilation error?







      linux glibc yocto bitbake microchip






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 22 '18 at 13:49









      Mike

      2,1702825




      2,1702825










      asked Nov 22 '18 at 8:32









      George SephtonGeorge Sephton

      61




      61
























          2 Answers
          2






          active

          oldest

          votes


















          2














          Get the package.



           MACHINE=at91sam9rlek bitbake glibc


          Clean



            MACHINE=at91sam9rlek bitbake -c clean glibc


          Compile the recipe



            MACHINE=at91sam9rlek bitbake -f -c compile glibc


          You can also specify the MACHINE definition. As I see, you use meta-atmel. You can set the MACHINE definition to according to your board.



          **Note:**Be sure that your meta-atmel version macthes with open-embedded and yocto poky version. It can be the root cause. Please, share the results.






          share|improve this answer


























          • The machine is set to sama5d27-som1-ek-sd in local.conf and I tried a forced compile as above using: MACHINE=sama5d27-som1-ek-sd bitbake -f -c compile glibc but this still produced the same error. The versions seem to be the same, I'm following the tutorial here: github.com/linux4sam/meta-atmel

            – George Sephton
            Nov 22 '18 at 11:49





















          0














          I cloned the rocko verison of meta-atmel to yocto folder and I just compiled glibc recipe successfully with the following commnad.



          MACHINE=sama5d27-som1-ek-sd bitbake -f -c compile glibc
          Parsing recipes: 100% |######################################################################################################################################################################| Time: 0:01:17
          Parsing of 2430 .bb files complete (0 cached, 2430 parsed). 3275 targets, 372 skipped, 37 masked, 0 errors.
          NOTE: Resolving any missing task queue dependencies

          Build Configuration:
          BB_VERSION = "1.36.0"
          BUILD_SYS = "x86_64-linux"
          NATIVELSBSTRING = "universal"
          TARGET_SYS = "arm-poky-linux-gnueabi"
          MACHINE = "sama5d27-som1-ek-sd"
          DISTRO = "poky"
          DISTRO_VERSION = "2.4.3"
          TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa5"
          TARGET_FPU = "hard"
          meta
          meta-poky
          meta-yocto-bsp = "rocko:05711ba18587aaaf4a9c465a1dd4537f27ceda93"
          meta-oe
          meta-multimedia
          meta-networking
          meta-python = "rocko:eae996301d9c097bcbeb8046f08041dc82bb62f8"
          meta-raspberrypi = "rocko:8e4c537d84fdde8e3b4642d0dda2c0f4af76d52f"
          meta-ti = "rocko:8ba46625b0630b738724e6697fd3520116b082ef"
          meta-freescale = "rocko:61ab34ac6d664a229847b796ec20fd9f7c8ecbf4"
          meta-qt5 = "rocko:682ad61c071a9710e9f9d8a32ab1b5f3c14953d1"
          meta-solidrun-arm-imx6 = "rocko:d567d75be8984bd868df9af6108f12fecb049c2d"
          meta-atmel = "rocko:f71ed8ade26b4f26f00b624bf1b6fdc6e6c4aaf0"

          NOTE: Tainting hash to force rebuild of task /home/eren/poky-rocko/meta/recipes-core/glibc/glibc_2.26.bb, do_compile | ETA: 0:00:00
          WARNING: /home/eren/poky-rocko/meta/recipes-core/glibc/glibc_2.26.bb.do_compile is tainted from a forced run | ETA: 0:00:00
          Initialising tasks: 100% |###################################################################################################################################################################| Time: 0:00:00
          NOTE: Executing SetScene Tasks
          NOTE: Executing RunQueue Tasks
          NOTE: Tasks Summary: Attempted 219 tasks of which 187 didn't need to be rerun and all succeeded.

          Summary: There was 1 WARNING message shown


          I think you problem is, your build environment is not clean or you do not use the same version of meta-atmel, open-embedded and poky or any depended meta.






          share|improve this answer
























          • I think you're right as I have done this successfully on a VM, I have just been given a freshly installed Ubuntu laptop which I've moved development onto. Is there anything that can be checked or re-installed related to the above?

            – George Sephton
            Nov 22 '18 at 16:18











          • You just need to be careful of using the same yocto-meta version and use the stable of community support level of yocto.

            – erenbasturk
            Nov 23 '18 at 12:27











          • I tried the build again but this time using rocko version instead of sumo and everything worked perfectly. Seems this may be a Microchip issue with compatibility then. Thanks for your help, using rocko will work fine for what I need.

            – George Sephton
            Dec 1 '18 at 17:00











          • Your welcome. I always try to use the community version of yocto or at least the closest stable version of yocto. The possibility of Having trouble is more less

            – erenbasturk
            Dec 1 '18 at 17:07












          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          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: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          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%2fstackoverflow.com%2fquestions%2f53426734%2fyocto-bitbake-glibc-build-fails%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          2














          Get the package.



           MACHINE=at91sam9rlek bitbake glibc


          Clean



            MACHINE=at91sam9rlek bitbake -c clean glibc


          Compile the recipe



            MACHINE=at91sam9rlek bitbake -f -c compile glibc


          You can also specify the MACHINE definition. As I see, you use meta-atmel. You can set the MACHINE definition to according to your board.



          **Note:**Be sure that your meta-atmel version macthes with open-embedded and yocto poky version. It can be the root cause. Please, share the results.






          share|improve this answer


























          • The machine is set to sama5d27-som1-ek-sd in local.conf and I tried a forced compile as above using: MACHINE=sama5d27-som1-ek-sd bitbake -f -c compile glibc but this still produced the same error. The versions seem to be the same, I'm following the tutorial here: github.com/linux4sam/meta-atmel

            – George Sephton
            Nov 22 '18 at 11:49


















          2














          Get the package.



           MACHINE=at91sam9rlek bitbake glibc


          Clean



            MACHINE=at91sam9rlek bitbake -c clean glibc


          Compile the recipe



            MACHINE=at91sam9rlek bitbake -f -c compile glibc


          You can also specify the MACHINE definition. As I see, you use meta-atmel. You can set the MACHINE definition to according to your board.



          **Note:**Be sure that your meta-atmel version macthes with open-embedded and yocto poky version. It can be the root cause. Please, share the results.






          share|improve this answer


























          • The machine is set to sama5d27-som1-ek-sd in local.conf and I tried a forced compile as above using: MACHINE=sama5d27-som1-ek-sd bitbake -f -c compile glibc but this still produced the same error. The versions seem to be the same, I'm following the tutorial here: github.com/linux4sam/meta-atmel

            – George Sephton
            Nov 22 '18 at 11:49
















          2












          2








          2







          Get the package.



           MACHINE=at91sam9rlek bitbake glibc


          Clean



            MACHINE=at91sam9rlek bitbake -c clean glibc


          Compile the recipe



            MACHINE=at91sam9rlek bitbake -f -c compile glibc


          You can also specify the MACHINE definition. As I see, you use meta-atmel. You can set the MACHINE definition to according to your board.



          **Note:**Be sure that your meta-atmel version macthes with open-embedded and yocto poky version. It can be the root cause. Please, share the results.






          share|improve this answer















          Get the package.



           MACHINE=at91sam9rlek bitbake glibc


          Clean



            MACHINE=at91sam9rlek bitbake -c clean glibc


          Compile the recipe



            MACHINE=at91sam9rlek bitbake -f -c compile glibc


          You can also specify the MACHINE definition. As I see, you use meta-atmel. You can set the MACHINE definition to according to your board.



          **Note:**Be sure that your meta-atmel version macthes with open-embedded and yocto poky version. It can be the root cause. Please, share the results.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 22 '18 at 9:27

























          answered Nov 22 '18 at 9:19









          erenbasturkerenbasturk

          33527




          33527













          • The machine is set to sama5d27-som1-ek-sd in local.conf and I tried a forced compile as above using: MACHINE=sama5d27-som1-ek-sd bitbake -f -c compile glibc but this still produced the same error. The versions seem to be the same, I'm following the tutorial here: github.com/linux4sam/meta-atmel

            – George Sephton
            Nov 22 '18 at 11:49





















          • The machine is set to sama5d27-som1-ek-sd in local.conf and I tried a forced compile as above using: MACHINE=sama5d27-som1-ek-sd bitbake -f -c compile glibc but this still produced the same error. The versions seem to be the same, I'm following the tutorial here: github.com/linux4sam/meta-atmel

            – George Sephton
            Nov 22 '18 at 11:49



















          The machine is set to sama5d27-som1-ek-sd in local.conf and I tried a forced compile as above using: MACHINE=sama5d27-som1-ek-sd bitbake -f -c compile glibc but this still produced the same error. The versions seem to be the same, I'm following the tutorial here: github.com/linux4sam/meta-atmel

          – George Sephton
          Nov 22 '18 at 11:49







          The machine is set to sama5d27-som1-ek-sd in local.conf and I tried a forced compile as above using: MACHINE=sama5d27-som1-ek-sd bitbake -f -c compile glibc but this still produced the same error. The versions seem to be the same, I'm following the tutorial here: github.com/linux4sam/meta-atmel

          – George Sephton
          Nov 22 '18 at 11:49















          0














          I cloned the rocko verison of meta-atmel to yocto folder and I just compiled glibc recipe successfully with the following commnad.



          MACHINE=sama5d27-som1-ek-sd bitbake -f -c compile glibc
          Parsing recipes: 100% |######################################################################################################################################################################| Time: 0:01:17
          Parsing of 2430 .bb files complete (0 cached, 2430 parsed). 3275 targets, 372 skipped, 37 masked, 0 errors.
          NOTE: Resolving any missing task queue dependencies

          Build Configuration:
          BB_VERSION = "1.36.0"
          BUILD_SYS = "x86_64-linux"
          NATIVELSBSTRING = "universal"
          TARGET_SYS = "arm-poky-linux-gnueabi"
          MACHINE = "sama5d27-som1-ek-sd"
          DISTRO = "poky"
          DISTRO_VERSION = "2.4.3"
          TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa5"
          TARGET_FPU = "hard"
          meta
          meta-poky
          meta-yocto-bsp = "rocko:05711ba18587aaaf4a9c465a1dd4537f27ceda93"
          meta-oe
          meta-multimedia
          meta-networking
          meta-python = "rocko:eae996301d9c097bcbeb8046f08041dc82bb62f8"
          meta-raspberrypi = "rocko:8e4c537d84fdde8e3b4642d0dda2c0f4af76d52f"
          meta-ti = "rocko:8ba46625b0630b738724e6697fd3520116b082ef"
          meta-freescale = "rocko:61ab34ac6d664a229847b796ec20fd9f7c8ecbf4"
          meta-qt5 = "rocko:682ad61c071a9710e9f9d8a32ab1b5f3c14953d1"
          meta-solidrun-arm-imx6 = "rocko:d567d75be8984bd868df9af6108f12fecb049c2d"
          meta-atmel = "rocko:f71ed8ade26b4f26f00b624bf1b6fdc6e6c4aaf0"

          NOTE: Tainting hash to force rebuild of task /home/eren/poky-rocko/meta/recipes-core/glibc/glibc_2.26.bb, do_compile | ETA: 0:00:00
          WARNING: /home/eren/poky-rocko/meta/recipes-core/glibc/glibc_2.26.bb.do_compile is tainted from a forced run | ETA: 0:00:00
          Initialising tasks: 100% |###################################################################################################################################################################| Time: 0:00:00
          NOTE: Executing SetScene Tasks
          NOTE: Executing RunQueue Tasks
          NOTE: Tasks Summary: Attempted 219 tasks of which 187 didn't need to be rerun and all succeeded.

          Summary: There was 1 WARNING message shown


          I think you problem is, your build environment is not clean or you do not use the same version of meta-atmel, open-embedded and poky or any depended meta.






          share|improve this answer
























          • I think you're right as I have done this successfully on a VM, I have just been given a freshly installed Ubuntu laptop which I've moved development onto. Is there anything that can be checked or re-installed related to the above?

            – George Sephton
            Nov 22 '18 at 16:18











          • You just need to be careful of using the same yocto-meta version and use the stable of community support level of yocto.

            – erenbasturk
            Nov 23 '18 at 12:27











          • I tried the build again but this time using rocko version instead of sumo and everything worked perfectly. Seems this may be a Microchip issue with compatibility then. Thanks for your help, using rocko will work fine for what I need.

            – George Sephton
            Dec 1 '18 at 17:00











          • Your welcome. I always try to use the community version of yocto or at least the closest stable version of yocto. The possibility of Having trouble is more less

            – erenbasturk
            Dec 1 '18 at 17:07
















          0














          I cloned the rocko verison of meta-atmel to yocto folder and I just compiled glibc recipe successfully with the following commnad.



          MACHINE=sama5d27-som1-ek-sd bitbake -f -c compile glibc
          Parsing recipes: 100% |######################################################################################################################################################################| Time: 0:01:17
          Parsing of 2430 .bb files complete (0 cached, 2430 parsed). 3275 targets, 372 skipped, 37 masked, 0 errors.
          NOTE: Resolving any missing task queue dependencies

          Build Configuration:
          BB_VERSION = "1.36.0"
          BUILD_SYS = "x86_64-linux"
          NATIVELSBSTRING = "universal"
          TARGET_SYS = "arm-poky-linux-gnueabi"
          MACHINE = "sama5d27-som1-ek-sd"
          DISTRO = "poky"
          DISTRO_VERSION = "2.4.3"
          TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa5"
          TARGET_FPU = "hard"
          meta
          meta-poky
          meta-yocto-bsp = "rocko:05711ba18587aaaf4a9c465a1dd4537f27ceda93"
          meta-oe
          meta-multimedia
          meta-networking
          meta-python = "rocko:eae996301d9c097bcbeb8046f08041dc82bb62f8"
          meta-raspberrypi = "rocko:8e4c537d84fdde8e3b4642d0dda2c0f4af76d52f"
          meta-ti = "rocko:8ba46625b0630b738724e6697fd3520116b082ef"
          meta-freescale = "rocko:61ab34ac6d664a229847b796ec20fd9f7c8ecbf4"
          meta-qt5 = "rocko:682ad61c071a9710e9f9d8a32ab1b5f3c14953d1"
          meta-solidrun-arm-imx6 = "rocko:d567d75be8984bd868df9af6108f12fecb049c2d"
          meta-atmel = "rocko:f71ed8ade26b4f26f00b624bf1b6fdc6e6c4aaf0"

          NOTE: Tainting hash to force rebuild of task /home/eren/poky-rocko/meta/recipes-core/glibc/glibc_2.26.bb, do_compile | ETA: 0:00:00
          WARNING: /home/eren/poky-rocko/meta/recipes-core/glibc/glibc_2.26.bb.do_compile is tainted from a forced run | ETA: 0:00:00
          Initialising tasks: 100% |###################################################################################################################################################################| Time: 0:00:00
          NOTE: Executing SetScene Tasks
          NOTE: Executing RunQueue Tasks
          NOTE: Tasks Summary: Attempted 219 tasks of which 187 didn't need to be rerun and all succeeded.

          Summary: There was 1 WARNING message shown


          I think you problem is, your build environment is not clean or you do not use the same version of meta-atmel, open-embedded and poky or any depended meta.






          share|improve this answer
























          • I think you're right as I have done this successfully on a VM, I have just been given a freshly installed Ubuntu laptop which I've moved development onto. Is there anything that can be checked or re-installed related to the above?

            – George Sephton
            Nov 22 '18 at 16:18











          • You just need to be careful of using the same yocto-meta version and use the stable of community support level of yocto.

            – erenbasturk
            Nov 23 '18 at 12:27











          • I tried the build again but this time using rocko version instead of sumo and everything worked perfectly. Seems this may be a Microchip issue with compatibility then. Thanks for your help, using rocko will work fine for what I need.

            – George Sephton
            Dec 1 '18 at 17:00











          • Your welcome. I always try to use the community version of yocto or at least the closest stable version of yocto. The possibility of Having trouble is more less

            – erenbasturk
            Dec 1 '18 at 17:07














          0












          0








          0







          I cloned the rocko verison of meta-atmel to yocto folder and I just compiled glibc recipe successfully with the following commnad.



          MACHINE=sama5d27-som1-ek-sd bitbake -f -c compile glibc
          Parsing recipes: 100% |######################################################################################################################################################################| Time: 0:01:17
          Parsing of 2430 .bb files complete (0 cached, 2430 parsed). 3275 targets, 372 skipped, 37 masked, 0 errors.
          NOTE: Resolving any missing task queue dependencies

          Build Configuration:
          BB_VERSION = "1.36.0"
          BUILD_SYS = "x86_64-linux"
          NATIVELSBSTRING = "universal"
          TARGET_SYS = "arm-poky-linux-gnueabi"
          MACHINE = "sama5d27-som1-ek-sd"
          DISTRO = "poky"
          DISTRO_VERSION = "2.4.3"
          TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa5"
          TARGET_FPU = "hard"
          meta
          meta-poky
          meta-yocto-bsp = "rocko:05711ba18587aaaf4a9c465a1dd4537f27ceda93"
          meta-oe
          meta-multimedia
          meta-networking
          meta-python = "rocko:eae996301d9c097bcbeb8046f08041dc82bb62f8"
          meta-raspberrypi = "rocko:8e4c537d84fdde8e3b4642d0dda2c0f4af76d52f"
          meta-ti = "rocko:8ba46625b0630b738724e6697fd3520116b082ef"
          meta-freescale = "rocko:61ab34ac6d664a229847b796ec20fd9f7c8ecbf4"
          meta-qt5 = "rocko:682ad61c071a9710e9f9d8a32ab1b5f3c14953d1"
          meta-solidrun-arm-imx6 = "rocko:d567d75be8984bd868df9af6108f12fecb049c2d"
          meta-atmel = "rocko:f71ed8ade26b4f26f00b624bf1b6fdc6e6c4aaf0"

          NOTE: Tainting hash to force rebuild of task /home/eren/poky-rocko/meta/recipes-core/glibc/glibc_2.26.bb, do_compile | ETA: 0:00:00
          WARNING: /home/eren/poky-rocko/meta/recipes-core/glibc/glibc_2.26.bb.do_compile is tainted from a forced run | ETA: 0:00:00
          Initialising tasks: 100% |###################################################################################################################################################################| Time: 0:00:00
          NOTE: Executing SetScene Tasks
          NOTE: Executing RunQueue Tasks
          NOTE: Tasks Summary: Attempted 219 tasks of which 187 didn't need to be rerun and all succeeded.

          Summary: There was 1 WARNING message shown


          I think you problem is, your build environment is not clean or you do not use the same version of meta-atmel, open-embedded and poky or any depended meta.






          share|improve this answer













          I cloned the rocko verison of meta-atmel to yocto folder and I just compiled glibc recipe successfully with the following commnad.



          MACHINE=sama5d27-som1-ek-sd bitbake -f -c compile glibc
          Parsing recipes: 100% |######################################################################################################################################################################| Time: 0:01:17
          Parsing of 2430 .bb files complete (0 cached, 2430 parsed). 3275 targets, 372 skipped, 37 masked, 0 errors.
          NOTE: Resolving any missing task queue dependencies

          Build Configuration:
          BB_VERSION = "1.36.0"
          BUILD_SYS = "x86_64-linux"
          NATIVELSBSTRING = "universal"
          TARGET_SYS = "arm-poky-linux-gnueabi"
          MACHINE = "sama5d27-som1-ek-sd"
          DISTRO = "poky"
          DISTRO_VERSION = "2.4.3"
          TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa5"
          TARGET_FPU = "hard"
          meta
          meta-poky
          meta-yocto-bsp = "rocko:05711ba18587aaaf4a9c465a1dd4537f27ceda93"
          meta-oe
          meta-multimedia
          meta-networking
          meta-python = "rocko:eae996301d9c097bcbeb8046f08041dc82bb62f8"
          meta-raspberrypi = "rocko:8e4c537d84fdde8e3b4642d0dda2c0f4af76d52f"
          meta-ti = "rocko:8ba46625b0630b738724e6697fd3520116b082ef"
          meta-freescale = "rocko:61ab34ac6d664a229847b796ec20fd9f7c8ecbf4"
          meta-qt5 = "rocko:682ad61c071a9710e9f9d8a32ab1b5f3c14953d1"
          meta-solidrun-arm-imx6 = "rocko:d567d75be8984bd868df9af6108f12fecb049c2d"
          meta-atmel = "rocko:f71ed8ade26b4f26f00b624bf1b6fdc6e6c4aaf0"

          NOTE: Tainting hash to force rebuild of task /home/eren/poky-rocko/meta/recipes-core/glibc/glibc_2.26.bb, do_compile | ETA: 0:00:00
          WARNING: /home/eren/poky-rocko/meta/recipes-core/glibc/glibc_2.26.bb.do_compile is tainted from a forced run | ETA: 0:00:00
          Initialising tasks: 100% |###################################################################################################################################################################| Time: 0:00:00
          NOTE: Executing SetScene Tasks
          NOTE: Executing RunQueue Tasks
          NOTE: Tasks Summary: Attempted 219 tasks of which 187 didn't need to be rerun and all succeeded.

          Summary: There was 1 WARNING message shown


          I think you problem is, your build environment is not clean or you do not use the same version of meta-atmel, open-embedded and poky or any depended meta.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 22 '18 at 13:41









          erenbasturkerenbasturk

          33527




          33527













          • I think you're right as I have done this successfully on a VM, I have just been given a freshly installed Ubuntu laptop which I've moved development onto. Is there anything that can be checked or re-installed related to the above?

            – George Sephton
            Nov 22 '18 at 16:18











          • You just need to be careful of using the same yocto-meta version and use the stable of community support level of yocto.

            – erenbasturk
            Nov 23 '18 at 12:27











          • I tried the build again but this time using rocko version instead of sumo and everything worked perfectly. Seems this may be a Microchip issue with compatibility then. Thanks for your help, using rocko will work fine for what I need.

            – George Sephton
            Dec 1 '18 at 17:00











          • Your welcome. I always try to use the community version of yocto or at least the closest stable version of yocto. The possibility of Having trouble is more less

            – erenbasturk
            Dec 1 '18 at 17:07



















          • I think you're right as I have done this successfully on a VM, I have just been given a freshly installed Ubuntu laptop which I've moved development onto. Is there anything that can be checked or re-installed related to the above?

            – George Sephton
            Nov 22 '18 at 16:18











          • You just need to be careful of using the same yocto-meta version and use the stable of community support level of yocto.

            – erenbasturk
            Nov 23 '18 at 12:27











          • I tried the build again but this time using rocko version instead of sumo and everything worked perfectly. Seems this may be a Microchip issue with compatibility then. Thanks for your help, using rocko will work fine for what I need.

            – George Sephton
            Dec 1 '18 at 17:00











          • Your welcome. I always try to use the community version of yocto or at least the closest stable version of yocto. The possibility of Having trouble is more less

            – erenbasturk
            Dec 1 '18 at 17:07

















          I think you're right as I have done this successfully on a VM, I have just been given a freshly installed Ubuntu laptop which I've moved development onto. Is there anything that can be checked or re-installed related to the above?

          – George Sephton
          Nov 22 '18 at 16:18





          I think you're right as I have done this successfully on a VM, I have just been given a freshly installed Ubuntu laptop which I've moved development onto. Is there anything that can be checked or re-installed related to the above?

          – George Sephton
          Nov 22 '18 at 16:18













          You just need to be careful of using the same yocto-meta version and use the stable of community support level of yocto.

          – erenbasturk
          Nov 23 '18 at 12:27





          You just need to be careful of using the same yocto-meta version and use the stable of community support level of yocto.

          – erenbasturk
          Nov 23 '18 at 12:27













          I tried the build again but this time using rocko version instead of sumo and everything worked perfectly. Seems this may be a Microchip issue with compatibility then. Thanks for your help, using rocko will work fine for what I need.

          – George Sephton
          Dec 1 '18 at 17:00





          I tried the build again but this time using rocko version instead of sumo and everything worked perfectly. Seems this may be a Microchip issue with compatibility then. Thanks for your help, using rocko will work fine for what I need.

          – George Sephton
          Dec 1 '18 at 17:00













          Your welcome. I always try to use the community version of yocto or at least the closest stable version of yocto. The possibility of Having trouble is more less

          – erenbasturk
          Dec 1 '18 at 17:07





          Your welcome. I always try to use the community version of yocto or at least the closest stable version of yocto. The possibility of Having trouble is more less

          – erenbasturk
          Dec 1 '18 at 17:07


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • 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%2fstackoverflow.com%2fquestions%2f53426734%2fyocto-bitbake-glibc-build-fails%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

          鏡平學校

          ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

          Why https connections are so slow when debugging (stepping over) in Java?