Bug 5289 - Verify that config.log is created whenever a package is built - config log is missing
Summary: Verify that config.log is created whenever a package is built - config log is...
Status: VERIFIED NOTABUG
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: configuration (show other bugs)
Version: 1.5
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.5
Assignee: Saul Wold
QA Contact: Ionut Chisanovici
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-09-30 08:13 UTC by Ionut Chisanovici
Modified: 2015-08-07 13:49 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ionut Chisanovici 2013-09-30 08:13:46 UTC 
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.
Comment 1 Saul Wold 2013-09-30 16:52:07 UTC 
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.
Comment 2 Ionut Chisanovici 2013-10-01 09:50:08 UTC 
Hi,

You were right.
I tried again with a clean env. on ubuntu and the config.log for perf is there.