Created attachment 3759 [details] Screenshot BUILD: 2.3 M4: rc4-381897c64069ea43d595380a3ae913bcc79cf7e1 ENVIRONMENT: Debian 4.3 x86_64, STEPS TO REPRODUCE: Download extensible toolchain from: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.3.rc4/toolchain/x86_64/poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.sh Set file permissions: $ chmod +x poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.sh Run: ./poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.sh - ACTUAL OUTCOME: Error: Incompatible SDK installer! Your host gcc version is 4.9 and this SDK was built by gcc higher version. See attached screenshot Make sure I have the latest version of GCC (4.9.2 in this case), Even so there is an incompatibility error. REPRODUCIBILITY : I tried 5 times making sure I updated the gcc WORKAROUND: I reviewed in the toolchain script there is this Line : SDK_GCC_VER=’ ’ , but in previous toolchain that worked for me this line appears like this SDK_GCC_VER=’ -4.8’.
(In reply to comment #0) > Created attachment 3759 [details] > Screenshot > > BUILD: 2.3 M4: rc4-381897c64069ea43d595380a3ae913bcc79cf7e1 > ENVIRONMENT: Debian 4.3 x86_64, > STEPS TO REPRODUCE: > > Download extensible toolchain from: > > http://autobuilder.yoctoproject.org/pub/releases/yocto-2.3.rc4/toolchain/ > x86_64/poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.sh > > Set file permissions: > > $ chmod +x poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.sh > > Run: > ./poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.sh > > - ACTUAL OUTCOME: > Error: Incompatible SDK installer! Your host gcc version is 4.9 and this SDK > was built by gcc higher version. > > See attached screenshot > > Make sure I have the latest version of GCC (4.9.2 in this case), > Even so there is an incompatibility error. > > > REPRODUCIBILITY : I tried 5 times making sure I updated the gcc > > WORKAROUND: I reviewed in the toolchain script there is this Line : > SDK_GCC_VER=’ ’ , but in previous toolchain that worked for me this line > appears like this SDK_GCC_VER=’ -4.8’. I works correctly if you manually set SDK_GCC_VER=’ -4.10’ right ??
I just did a test on my local machine $ bitbake core-image-sato-sdk -c do_populate_sdk_ext and file poky-glibc-x86_64-core-image-sato-sdk-i586-toolchain-ext-2.3.sh that was created has correctly set GCC version "SDK_GCC_VER='-4.8'".
This could be an issue with the worker of the AB that created the toolchain.
(In reply to comment #1) > (In reply to comment #0) > > Created attachment 3759 [details] > > Screenshot > > > > BUILD: 2.3 M4: rc4-381897c64069ea43d595380a3ae913bcc79cf7e1 > > ENVIRONMENT: Debian 4.3 x86_64, > > STEPS TO REPRODUCE: > > > > Download extensible toolchain from: > > > > http://autobuilder.yoctoproject.org/pub/releases/yocto-2.3.rc4/toolchain/ > > x86_64/poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.sh > > > > Set file permissions: > > > > $ chmod +x poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.sh > > > > Run: > > ./poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.sh > > > > - ACTUAL OUTCOME: > > Error: Incompatible SDK installer! Your host gcc version is 4.9 and this SDK > > was built by gcc higher version. > > > > See attached screenshot > > > > Make sure I have the latest version of GCC (4.9.2 in this case), > > Even so there is an incompatibility error. > > > > > > REPRODUCIBILITY : I tried 5 times making sure I updated the gcc > > > > WORKAROUND: I reviewed in the toolchain script there is this Line : > > SDK_GCC_VER=’ ’ , but in previous toolchain that worked for me this line > > appears like this SDK_GCC_VER=’ -4.8’. > > I works correctly if you manually set SDK_GCC_VER=’ -4.10’ right ?? Yes if I modify this SDK_GCC_VER=’ -4.10’ it works OK
Bug 10832 (the gcc issue and fix) and Bug 10881 (the check on install and warning)‚cover this issue. Since it is an gcc version incompatibility, the best we can do is check for an inconsistency and warn+exit which we do. We will add an explanation to the releaase notes as well. Hopefully, by next release the gcc versions will have moved forward enough that this a very rare issue in the wild.