Building with ICECC provides 22 warnings. When adding ICECC to a local.conf with: INHERIT += "icecc" even the a simple 'bitbake core-image-minimal' displays: 22 warnings. See bellow the log. bitbake core-image-minimal Loading cache: 100% |######################################################################| ETA: 00:00:00 Loaded 1302 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.31.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-14.04" TARGET_SYS = "i586-poky-linux" MACHINE = "qemux86" DISTRO = "poky" DISTRO_VERSION = "2.1+snapshot-20160511" TUNE_FEATURES = "m32 i586" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "master:7ca60ec8bff7656b4e52f5a4d238913e851da089" NOTE: Preparing RunQueue NOTE: Checking sstate mirror object availability (for 688 objects) NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks WARNING: icecc-create-env-native-0.1-r2 do_configure: Cannot use icecc: invalid ICECC_ENV_EXEC WARNING: icecc-create-env-native-0.1-r2 do_compile: Cannot use icecc: invalid ICECC_ENV_EXEC WARNING: icecc-create-env-native-0.1-r2 do_install: Cannot use icecc: invalid ICECC_ENV_EXEC WARNING: base-files-3.0.14-r89 do_configure: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: base-files-3.0.14-r89 do_compile: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: depmodwrapper-cross-1.0-r0 do_configure: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: depmodwrapper-cross-1.0-r0 do_compile: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: shadow-securetty-4.2.1-r3 do_configure: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: shadow-securetty-4.2.1-r3 do_compile: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: qemuwrapper-cross-1.0-r0 do_configure: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: qemuwrapper-cross-1.0-r0 do_compile: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: sysvinit-inittab-2.88dsf-r10 do_configure: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: sysvinit-inittab-2.88dsf-r10 do_compile: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: linux-libc-headers-4.4-r0 do_configure: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: linux-libc-headers-4.4-r0 do_compile: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: depmodwrapper-cross-1.0-r0 do_install: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: linux-libc-headers-4.4-r0 do_install: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: qemuwrapper-cross-1.0-r0 do_install: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: shadow-securetty-4.2.1-r3 do_install: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: base-files-3.0.14-r89 do_install: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: sysvinit-inittab-2.88dsf-r10 do_install: Cannot use icecc: could not get ICECC_CC or ICECC_CXX WARNING: glibc-locale-2.23-r0 do_install: Cannot use icecc: could not get ICECC_CC or ICECC_CXX NOTE: Tasks Summary: Attempted 2061 tasks of which 9 didn't need to be rerun and all succeeded. Summary: There were 22 WARNING messages shown
Hi Bogdan, just wondering if this bug came up as part of a test, if so, which is it?
Benjamin: I discovered this when verifying bug 8934. More information: In mega-manual we have:"If ICECC_ENV_EXEC is set in your local.conf file, the variable should point to the icecc-create-env script provided by the user. If you do not point to a user-provided script, the build system uses the default script provided by the recipe icecc-create-env-native.bb." I have not defined variable ICECC_ENV_EXEC; so default mechanism seems not to work.
Joshua, since you use this could you confirm if this was fixed please?
The warning is a little misleading; icecc is probably working its just not being used for those specific recipes because they don't specify a compiler. The warning probably needs to be adjusted to not show up in those sorts of cases where it is expected. I think doing that should be pretty straight forward
i believe this was resolved in oe-core 0315aabeff8e6483b737d0e23d6841f1394ad3c8.
Resolved in 0315aabeff8e6483b737d0e23d6841f1394ad3c8