Tree/Branch: Poky/Master Poky Commit: 2163461ec94528ecf046a04edc5db3d2dd3a6b8b On autobuilder, latest build against master branch fails to build toolchain for qemuarm/mips/ppc. The same error does not happen on local build. Details could be found on http://autobuilder.pokylinux.org:8010/builders/nightly-external-toolchain/builds/17/steps/shell_6/logs/stdio. (qemuarm as example) Part of error log is as below: ######## | checking whether ln works... yes | checking whether ln -s works... yes | checking for a sed that does not truncate output... /bin/sed | checking for gawk... gawk | checking for i686-pokysdk-linux-gcc... ccache i686-pokysdk-linux-gcc -march=i686 --sysroot=/builds2/pokybuild/nightly-external-toolchain/build/build/tmp/sysroots/i686-nativesdk-pokysdk-linux | checking for C compiler default output file name... | configure: error: in `/builds2/pokybuild/nightly-external-toolchain/build/build/tmp/work/i686-nativesdk-pokysdk-linux/gcc-cross-canadian-arm-4.6.0-r3/gcc-4.6.0/build.i686-pokysdk-linux.arm-poky-linux-gnueabi': | configure: error: C compiler cannot create executables | See `config.log' for more details. | ERROR: oe_runconf failed | ERROR: Function 'do_configure' failed (see /builds2/pokybuild/nightly-external-toolchain/build/build/tmp/work/i686-nativesdk-pokysdk-linux/gcc-cross-canadian-arm-4.6.0-r3/temp/log.do_configure.18614 for further information) | ERROR: Function 'do_configure' failed (see /builds2/pokybuild/nightly-external-toolchain/build/build/tmp/work/i686-nativesdk-pokysdk-linux/gcc-cross-canadian-arm-4.6.0-r3/temp/log.do_configure.18614 for further information) NOTE: package gcc-cross-canadian-arm-4.6.0-r3: task do_configure: Failed ERROR: Task 1329 (/builds2/pokybuild/nightly-external-toolchain/build/meta/recipes-devtools/gcc/gcc-cross-canadian_4.6.0.bb, do_configure) failed with exit code '1' ERROR: '/builds2/pokybuild/nightly-external-toolchain/build/meta/recipes-devtools/gcc/gcc-cross-canadian_4.6.0.bb' failed ########
I do not see same error with latest build on autobuilder. So suppose it has been fixed. Verify the bug as fixed on autobuilder with following commit: Branch: master Commit: a1f79a7896b6411669b3ccada6204d2695e80fc5
Verify the bug as fixed.