Bug 9177 - Failed to install jethro eSDK image from Autobuilder
Summary: Failed to install jethro eSDK image from Autobuilder
Status: RESOLVED WONTFIX
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 2.0.1
Hardware: x86 Multiple
: Medium+ major
Target Milestone: 2.2 M1
Assignee: Paul Eggleton
QA Contact: Francisco Pedraza
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-02-26 15:59 UTC by Valentin Hangan
Modified: 2016-06-17 17:03 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments
preparing-build-system-log (221.21 KB, application/octet-stream)
2016-02-26 15:59 UTC, Valentin Hangan
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Valentin Hangan 2016-02-26 15:59:20 UTC
Created attachment 3007 [details]
preparing-build-system-log

Steps:

1. Download eSDK images from autobuilder: http://autobuilder.yoctoproject.org/pub/releases/CURRENT/toolchain/x86_64/
 - poky-glibc-x86_64-core-image-minimal-core2-64-toolchain-ext-2.0.1.sh
 - poky-glibc-x86_64-core-image-minimal-armv5e-toolchain-ext-2.0.1.sh
2. Run script to install image

Results:

checking for the correct version of the gmp/mpfr/mpc libraries... no
| configure: error: Building GCC requires GMP 4.2+, MPFR 2.4.0+ and MPC 0.8.0+.
| Try the --with-gmp, --with-mpfr and/or --with-mpc options to specify
| their locations.  Source code for these libraries can be found at
| their respective hosting sites as well as at
| ftp://gcc.gnu.org/pub/gcc/infrastructure/.  See also
| http://gcc.gnu.org/install/prerequisites.html for additional info.  If
| you obtained GMP, MPFR and/or MPC from a vendor distribution package,
| make sure that you have installed both the libraries and the header
| files.  They may be located in separate packages.
| Configure failed. The contents of all config.log files follows to aid debugging
| /home/valentin/AVB/armv5e/tmp/work/x86_64-linux/gcc-cross-initial-i586/5.2.0-r0/gcc-5.2.0/build.x86_64-linux.i586-poky-linux/config.log
| This file contains any messages produced by compilers while
| running configure, to aid debugging if configure makes a mistake.
|
| It was created by configure, which was
| generated by GNU Autoconf 2.64.  Invocation command line was
|
|   $ /home/valentin/AVB/armv5e/tmp/work-shared/gcc-5.2.0-r0/gcc-5.2.0/configure --build=x86_64-linux --host=x86_64-linux --target=i586-poky-linux --prefix=/home/valentin/AVB/armv5e/tmp/sysroots/x86_64-linux/usr --exec_prefix=/home/valentin/AVB/armv5e/tmp/sysroots/x86_64-linux/usr --bindir=/home/valentin/AVB/armv5e/tmp/sysroots/x86_64-linux/usr/bin/i586-poky-linux.gcc-cross-initial-i586 --sbindir=/home/valentin/AVB/armv5e/tmp/sysroots/x86_64-linux/usr/bin/i586-poky-linux.gcc-cross-initial-i586 --libexecdir=/home/valentin/AVB/armv5e/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux.gcc-cross-initial-i586 --datadir=/home/valentin/AVB/armv5e/tmp/sysroots/x86_64-linux/usr/share --sysconfdir=/home/valentin/AVB/armv5e/tmp/sysroots/x86_64-linux/etc --sharedstatedir=/home/valentin/AVB/armv5e/tmp/sysroots/x86_64-linux/com --localstatedir=/home/valentin/AVB/armv5e/tmp/sysroots/x86_64-linux/var --libdir=/home/valentin/AVB/armv5e/tmp/sysroots/x86_64-linux/usr/lib/i586-poky-linux.gcc-cross-initial-i586 --includedir=/home/valentin/AVB/armv5e/tmp/sysroots/x86_64-linux/usr/include --oldincludedir=/home/valentin/AVB/armv5e/tmp/sysroots/x86_64-linux/usr/include --infodir=/home/valentin/AVB/armv5e/tmp/sysroots/x86_64-linux/usr/share/info --mandir=/home/valentin/AVB/armv5e/tmp/sysroots/x86_64-linux/usr/share/man --disable-silent-rules --disable-dependency-tracking --with-libtool-sysroot=/home/valentin/AVB/armv5e/tmp/sysroots/x86_64-linux --with-newlib --without-headers --disable-shared --disable-threads --disable-multilib --disable-__cxa_atexit --enable-languages=c --enable-target-optspace --program-prefix=i586-poky-linux- --with-sysroot=/not/exist --with-build-sysroot=/home/valentin/AVB/armv5e/tmp/work/x86_64-linux/gcc-cross-initial-i586/5.2.0-r0/gcc-5.2.0/build.x86_64-linux.i586-poky-linux/tmpsysroot --disable-libmudflap --disable-libgomp --disable-libssp --disable-libquadmath --with-system-zlib --disable-lto --disable-plugin --enable-decimal-float=no --without-isl --with-native-system-header-dir=/usr/include --disable-nls --enable-__cxa_atexit
|
| ## --------- ##
| ## Platform. ##
| ## --------- ##
|
| hostname = vhanganx-PC3
| uname -m = x86_64
| uname -r = 4.1.13-100.fc21.x86_64
| uname -s = Linux
| uname -v = #1 SMP Tue Nov 10 13:13:20 UTC 2015
|

 configure: exit 1
| ERROR: oe_runconf failed
| ERROR: Function failed: do_configure (log file is located at /home/valentin/AVB/armv5e/tmp/work/x86_64-linux/gcc-cross-initial-i586/5.2.0-r0/temp/log.do_configure.32723)
NOTE: recipe gcc-cross-initial-i586-5.2.0-r0: task do_configure: Failed
ERROR: Task 988 (/home/valentin/AVB/armv5e/layers/build/meta/recipes-devtools/gcc/gcc-cross-initial_5.2.bb, do_configure) failed with exit code '1'
NOTE: recipe linux-yocto-4.1.17+gitAUTOINC+46bb64d605_2e0ac7b6c4-r0: task do_fetch: Succeeded
NOTE: Tasks Summary: Attempted 1279 tasks of which 780 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/valentin/AVB/armv5e/layers/build/meta/recipes-devtools/gcc/gcc-cross-initial_5.2.bb, do_configure
Summary: There were 2 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.



3. Install packages for gmp and mpc and i have same error.
   Ubuntu : libmpc-dev,libgmp-dev
   Fedora 21 : libmpc-devel, gmpc-devel

Commit: b1f23d1254682866236bfaeb843c0d8aa332efc2
Comment 1 Bogdan Alexandru Voiculescu 2016-03-04 05:33:24 UTC
2.1 eSDK builds are working fine. 
I suggest to correct the milestone to 2.0.2, if it supported.
Comment 2 Paul Eggleton 2016-06-14 01:37:42 UTC
I don't think it's really practical for us to fix this - there are too many moderately invasive fixes to be backported to jethro in order to make the installer work properly. If there's a real need we can do it, but for now I'm going to say let's leave it as unsupported.