Bug 12637

Summary: [2.5 M3 RC1] Build appliance failed on glibc-initial do_configure when bitbake core-image-minimal
Product: [Build System, Metadata & Runtime] Runtime Reporter: yeoh ee peng <ee.peng.yeoh>
Component: build-applianceAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium+ CC: richard.purdie, stephano
Version: 2.5   
Target Milestone: 4.99   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
Error-glibc-initial-do_configure none

Description yeoh ee peng 2018-03-30 01:27:57 UTC 
Created attachment 4244 [details]
Error-glibc-initial-do_configure

Step to reproduce error:
1) Download the build-appliance image from New Autobuilder
http://autobuilder.yoctoproject.org/pub/yocto-2.5_M3.rc1/build-appliance/Yocto_Build_Appliance.zip

2) Boot up build appliance image using VMWare on Ubuntu host machine

3) Using build appliance, bitbake core-image-minimal 

ERROR: glibc-initial-2.26-r0 do_configure: Function failed: do_configure
Comment 1 Richard Purdie 2018-03-30 02:05:19 UTC 
/home/builder/poky/build/tmp/work/i586-poky-linux/glibc-initial/2.26-r0/recipe-sysroot-native/usr/bin/i586-poky-linux.gcc-cross-initial-i586/../../libexec/i586-poky-linux.gcc-cross-initial-i586/gcc/i586-poky-linux/7.2.0/ld: /home/builder/poky/build/tmp/sysroots-uninative/x86_64-linux/lib/libc.so.6: version `GLIBC_2.27' not found (required by /home/builder/poky/build/tmp/work/i586-poky-linux/glibc-initial/2.26-r0/recipe-sysroot-native/usr/bin/i586-poky-linux.gcc-cross-initial-i586/../../libexec/i586-poky-linux.gcc-cross-initial-i586/gcc/i586-poky-linux/7.2.0/ld)

I suspect the version from the new autobuilder was built with an old SRCREV of the metadata.
Comment 2 Juro Bystricky 2018-04-04 12:59:19 UTC 
I rebuilt Build Appliance locally on my machine with "sumo". I modified SRCREV in the recipe to point to to the top "sumo" commit.
I built BA, ran it in VirtualBox. Within the BA I built core-image-sato. Then I was able to run:

$ runqemu core-image-sato 

within the BA as well.

(There was one warning while building the image regarding the Host Distribution poky-snapshot not being validated.)
Comment 3 Richard Purdie 2018-07-07 12:54:57 UTC 
I investigated the behaviour differences between the older buildbot codebase and the newer one and found the defaults were different. I've fixed difference which resolves this bug (which was caused by old/stale versions from a build on the new codebase).