Bug 1720 - [BSP build] gcc-runtime/eglibc do_configure failed with sanity check
Summary: [BSP build] gcc-runtime/eglibc do_configure failed with sanity check
Status: RESOLVED WORKSFORME
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium major
Target Milestone: 1.2 M1
Assignee: Nitin Kamble
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-11-02 23:28 UTC by Jiajun Xu
Modified: 2011-12-15 09:07 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

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 Jiajun Xu 2011-11-02 23:28:30 UTC 
MACHINE: sugarbay/n450
poky/branch:stage/master_under_test:3287666339088a6a01bcb5890a47863d7f5608b7
meta-intel: master:63253211b4ca30c3a5fa2b4dd9a393247217816e

MACHINE: crownbay-noemgd/emenlow
poky/branch:master:9b76e6a2cfc5a4d779f3b06e3acc5ff7b8275470
meta-intel: master:63253211b4ca30c3a5fa2b4dd9a393247217816e

With latest autobuilder, above BSP build failed during do_configure for gcc-runtime/eglibc. The error log is as below:

As an example, sugarbay log could be found on http://autobuilder.pokylinux.org:8010/builders/sugarbay/builds/37/steps/shell_14/logs/stdio.

#######
| checking for C compiler default output file name... a.out
| checking whether the C compiler works... yes
| checking whether we are cross compiling... yes
| checking for suffix of executables...
| checking for suffix of object files... o
| checking whether we are using the GNU C compiler... yes
| checking whether x86_64-poky-linux-gcc    -m64 --sysroot=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/sugarbay/build/build/tmp/sysroots/sugarbay accepts -g... yes
| checking for x86_64-poky-linux-gcc    -m64 --sysroot=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/sugarbay/build/build/tmp/sysroots/sugarbay option to accept ISO C89... none needed
| checking for style of include used by make... GNU
| checking dependency style of x86_64-poky-linux-gcc    -m64 --sysroot=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/sugarbay/build/build/tmp/sysroots/sugarbay... none
| checking how to run the C preprocessor... x86_64-poky-linux-gcc -E --sysroot=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/sugarbay/build/build/tmp/sysroots/sugarbay    -m64
| configure: error: in `/srv/home/pokybuild/yocto-autobuilder/yocto-slave/sugarbay/build/build/tmp/work/x86_64-poky-linux/gcc-runtime-4.6.1+svnr180099-r16/gcc-4_6-branch/build.x86_64-poky-linux.x86_64-poky-linux/libssp':
| configure: error: C preprocessor "x86_64-poky-linux-gcc -E --sysroot=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/sugarbay/build/build/tmp/sysroots/sugarbay    -m64" fails sanity check
| See `config.log' for more details.
#######
Comment 1 Nitin Kamble 2011-11-30 10:16:56 UTC 
can you provide steps to reproduce the issues?
Comment 2 Jiajun Xu 2011-12-05 07:09:00 UTC 
(In reply to comment #1)
> can you provide steps to reproduce the issues?

Hi Nitin,
I have not tried it on local machine. But it always happens on autobuilder server.

As an example, sugarbay log could be found on
http://autobuilder.pokylinux.org:8010/builders/sugarbay/builds/37/steps/shell_14/logs/stdio.
Comment 3 Nitin Kamble 2011-12-15 09:07:13 UTC 
It looks as if these bugs are resolved, possibly due to stabilization of Shared State.  Since the builds are now working on the Autobuilder and that was where these failures where occurring, I think we can close them.