[yocto] Fedora 18 CentOS 6.4 yocto difference

Mon Jul 1 05:37:13 PDT 2013

Hello,
I build images for beagleboard, pandaboard, and beaglebone.  The base
core-image-sato-sdk with the additonal
boost qt-mobility-x11 gsl gnuplot gnuradio
openjdk-7-jdk openjdk-7-jre openjdk-7-vm-jamvm openjdk-7-vm-cacao
python-netserver

Build Configuration:
BB_VERSION        = "1.18.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Fedora-18"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "pandaboard"
DISTRO            = "poky"
DISTRO_VERSION    = "1.4.1"
TUNE_FEATURES     = "armv7a vfp neon"
TARGET_FPU        = "vfp-neon"
meta
meta-yocto        = "dylan:73f103bf9b2cdf985464dc53bf4f1cfd71d4531f"
meta-ti           = "(nobranch):d61bfa88ed3df9190ac9fd5643c27f77b34c5f01"
meta-oe           = "master:ed84e64d22400595b68da4e75b48ab7ecc342aa9"
meta-java         = "master:59696d89fd33df6953dcb2dd54ccd3b362513f28"
meta-yocto-bsp    = "dylan:73f103bf9b2cdf985464dc53bf4f1cfd71d4531f"
These build okay on a Fedora18 x86_64.
On CentOS-6.4-x86_64 I have a problem building the same images. The problem
is with numpy which is required by gnuradio.
This is the error that I get.
| /usr/bin/gfortran -Wall -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed
build/temp.linux-x86_64-2.7/numpy/linalg/lapack_litemodule.o
build/temp.linux-x86_64-2.7/numpy/linalg/python_xerbla.o -L/usr/lib64
-L/home/vidal/POKY/build062913_dylan/poky/build/tmp/sysroots/beagleboard/usr/lib
-Lbuild/temp.linux-x86_64-2.7 -llapack -lblas -lpython2.7 -lgfortran -o
build/lib.linux-x86_64-2.7/numpy/linalg/lapack_lite.so
| ERROR: Function failed: do_compile (see
/home/vidal/POKY/build062913_dylan/poky/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/python-numpy/1.7.0-r0/temp/log.do_compile.11041
for further information)
ERROR: Task 1470
(/home/vidal/POKY/build062913_dylan/poky/meta-oe/meta-oe/recipes-devtools/python/
python-numpy_1.7.0.bb, do_compile) failed with exit code '1'

If I remove gnuradio I get a rootfs.
NOTE: Tasks Summary: Attempted 7827 tasks of which 681 didn't need to be
rerun and all succeeded.

Summary: There were 11 WARNING messages shown.

After I transfer to a mmc these boot okay.
I am thinking that it is python or gcc that is the problem.
I have found some sites that show how to upgrade Centos 6.4 to a new python
and gcc.  These install in non-standard locations.  Does anyone know how to
tell bitbake where these non-standard locations are located?

The version of python on the CentOS-6.4-x86_64 is
python-2.6.6-36.el6.x86_64.
How to install Python 2.7 and 3.3 on CentOS 6 is at the site below.
                                                              1,1
Top
http://toomuchdata.com/2012/06/25/how-to-install-python-2-7-3-on-centos-6-2/
After running the commands above your newly installed Python interpreter
will be available as /usr/local/bin/python2.7 or /usr/local/bin/python3.3.
The system version of Python 2.6.6 will continue to be available as
/usr/bin/python and /usr/bin/python2.6.
This now has both python 2.6 and python 2.7.  Is this the direction that I
should be trying?

Installing gcc-4.7
cd /etc/yum.reps.d
wget http://people.centos.org/tru/devtools-1.1/devtools-1.1.repo

[testing-1.1-devtools-$releasever]
name=testing 1.1 devtools for CentOS $releasever
baseurl=http://people.centos.org/tru/devtools-1.1/$releasever/$basearch/RPMS
gpgcheck=0

yum --enablerepo=testing-1.1-devtools-6 install devtoolset-1.1-gcc
devtoolset-1.1-gcc-c++ devtoolset-1.1-gcc-gfortran
Installed:
  devtoolset-1.1-gcc.x86_64 0:4.7.2-5.el6
  devtoolset-1.1-gcc-c++.x86_64 0:4.7.2-5.el6
  devtoolset-1.1-gcc-gfortran.x86_64 0:4.7.2-5.el6

Dependency Installed:
  devtoolset-1.1-libquadmath-devel.x86_64 0:4.7.2-5.el6
  devtoolset-1.1-libstdc++-devel.x86_64 0:4.7.2-5.el6
  devtoolset-1.1-runtime.noarch 0:1-13.el6

Complete!

export CPP=/opt/centos/devtoolset-1.1/root/usr/bin/cpp
export CXX=/opt/centos/devtoolset-1.1/root/usr/bin/c++
export CC=/opt/centos/devtoolset-1.1/root/usr/bin/gcc

This is the default gfortran
 gfortran -v
Using built-in specs.
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla
--enable-bootstrap --enable-shared --enable-threads=posix
--enable-checking=release --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-gnu-unique-object
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk
--disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre
--enable-libgcj-multifile --enable-java-maintainer-mode
--with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib
--with-ppl --with-cloog --with-tune=generic --with-arch_32=i686
--build=x86_64-redhat-linux
Thread model: posix
gcc version 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC)
This is the non-standard gfortran
 /opt/centos/devtoolset-1.1/root/usr/bin/gfortran -v
Using built-in specs.
COLLECT_GCC=/opt/centos/devtoolset-1.1/root/usr/bin/gfortran
COLLECT_LTO_WRAPPER=/opt/centos/devtoolset-1.1/root/usr/libexec/gcc/x86_64-redhat-linux/4.7.2/lto-wrapper
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/opt/centos/devtoolset-1.1/root/usr
--mandir=/opt/centos/devtoolset-1.1/root/usr/share/man
--infodir=/opt/centos/devtoolset-1.1/root/usr/share/info
--with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap
--enable-shared --enable-threads=posix --enable-checking=release
--disable-build-with-cxx --disable-build-poststage1-with-cxx
--with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions
--enable-gnu-unique-object --enable-linker-build-id
--enable-languages=c,c++,fortran,lto --enable-plugin
--with-linker-hash-style=gnu --enable-initfini-array --disable-libgcj
--with-ppl --with-cloog
--with-mpc=/home/centos/rpm/BUILD/gcc-4.7.2-20121015/obj-x86_64-redhat-linux/mpc-install
--with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux
Thread model: posix
gcc version 4.7.2 20121015 (Red Hat 4.7.2-5) (GCC)
Any and all help will be appreciated.
thanks
Ed Vidal
vidal.develone at gmail.com or develone at sbcgloabol.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20130701/30c1f70a/attachment.html>