5289 2013-09-30 08:13:46 +0000 Verify that config.log is created whenever a package is built - config log is missing 2015-08-07 13:49:21 +0000 1 1 7 Build System, Metadata & Runtime OE-Core configuration 1.5 x86 Multiple VERIFIED NOTABUG Medium normal 1.5 1 ionutx.chisanovici sgw bogdanx.a.voiculescu sgw ionutx.chisanovici --- --- No (bug/feature does not impact docs) oldest_to_newest 37327 0 ionutx.chisanovici 2013-09-30 08:13:46 +0000 STATUS: RUNNING BUILD: 1.5_M5_RC5: 4d8ab87d25ea6e59dc88375813ef88ee0ac813d0 ENVIRONMENT: Multiple environments STEPS TO REPRODUCE: 1. Run bitbake <package_name> EXPECTED OUTCOME: Verify that config.log file exists in tmp/work/<ARCHITECTURE>/<package_version>/tests/. E.g: for perf - ${BUILD_DIR}/tmp/work/x86_64-linux/gperf-native-3.0.4-r0/gperf-3.0.4/tests/config.log . ACTUAL OUTCOME: Tried "bitbake man" and "bitbake perf" packages and no config logs were generated. 37363 1 sgw 2013-09-30 16:52:07 +0000 You may be looking in the wrong place. Many packages are now using a separate build and source directories. So the config.log files would be present under the ${WORKDIR}/build/... not ${WORKDIR}/gperf-3.0.4/ from the example below. check: ${BUILD_DIR}/tmp/work/x86_64-linux/gperf-native/3.0.4-r0/build/tests/config.log Also note you mention gperf-native-3.0.4-r0, that's an old package workdir, we now split the package name and version into directories. I do not believe this is a valid bug. 37385 2 ionutx.chisanovici 2013-10-01 09:50:08 +0000 Hi, You were right. I tried again with a clean env. on ubuntu and the config.log for perf is there.