Error when baking yocto for galileo

[Michal_Pawlowski]

Hi folks,

I was following Sergey's tutrial http://www.malinov.com/Home/sergey-s-blog/intelgalileo-buildinglinuximage on building yocto linux for galileo, part "Basic Steps to Rebuild The Image" and every time I get an error during python-numpy compilation (see attachment). Does anybody knows what is going on?

Btw. attached file was in $BUILD_DIR/tmp/work/i586-poky-linux-uclibc/python-numpy/1.7.0-r0/temp/

Best,

Michal

[Michal_Pawlowski]

I didn't figure it out yet, but obviously it looks like python-numpy compilation is causing this problem. So I naively thought that I can just remote it from the build. Learned, that I can get a dependency graph with

bitbake -g -u depexp python-numpy

but I still don't know how to disable single recipe from building - tried:

1. Brute-force way and just removed python-numpy from meta-oe/meta-oe/recipes-devtool - but getting bunch of errors
2. Tried to disable it by adding recipe to PACKAGE_EXCLUDE in bblayers.conf and layer.conf but no luck

[Brendan_L_Intel]

The iot-devkit image sources are here: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-iot-devkit/

What you are referring to are the 0.7.5 sources which ship with the galileo board and are different.

[Michal_Pawlowski]

Thanks Brendan. I'll try to build meta-intel-iot-devkit layer tonight.

Btw, how do I build dev tools for galileo so I can compile and link C code on my ubuntu to run on galileo board?

[Brendan_L_Intel]

You should be able to do that fairly easily following these instructions:

http://www.yoctoproject.org/docs/current/adt-manual/adt-manual.html#using-the-adt-installer

FYI: if you download this tarball (http://iotdk.intel.com/src/1.0/iotdk_src_140220.tar.gz) you'll get sstate binaries for 64bit which should enable really fast builds), it's the same sources as on git.

[Michal_Pawlowski]

Brendan Le Foll (Intel) wrote:

The iot-devkit image sources are here: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-iot-devkit/

What you are referring to are the 0.7.5 sources which ship with the galileo board and are different.

Unfortunately when trying to run build on master and devkit-mwc branches I was getting bunch of errors right at the start, see https://gist.github.com/misza222/9299258

[Michal_Pawlowski]

Brendan Le Foll (Intel) wrote:

You should be able to do that fairly easily following these instructions:

http://www.yoctoproject.org/docs/current/adt-manual/adt-manual.html#usin...

FYI: if you download this tarball (http://iotdk.intel.com/src/1.0/iotdk_src_140220.tar.gz) you'll get sstate binaries for 64bit which should enable really fast builds), it's the same sources as on git.

Thanks Brendan.

I read that part of yocto documentation that touches on development environment. My understanding is that I need to build image and dev tools using bitbake, is that correct?

And that tarball, with precompiled bits and pieces is great - no errors when building and fast.

[Brendan_L_Intel · Accepted solution]

Michal P. wrote:

Quote:

Brendan Le Foll (Intel) wrote:

The iot-devkit image sources are here: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-iot-devkit/

What you are referring to are the 0.7.5 sources which ship with the galileo board and are different.

Unfortunately when trying to run build on master and devkit-mwc branches I was getting bunch of errors right at the start, see https://gist.github.com/misza222/9299258

Ah yes - that's an easy fix, you need to go to your build/conf/local.conf and change the DISTRO variable. It's set to "locked" by default to do sstate builds but if you want to do a full source build without sstate you need to set it to "iot-devkit".

From: DISTRO ?= "iot-devkit-locked"

To: DISTRO ?= "iot-devkit"

[Brendan_L_Intel]

Michal P. wrote:

I read that part of yocto documentation that touches on development environment. My understanding is that I need to build image and dev tools using bitbake, is that correct?

Correct, we build our is SDK with "bitbake -c populate_sdk iot-devkit-prof-dev-image" and that gives you a large .sh which I believe you can install. See the documentation section 2.4.

http://www.yoctoproject.org/docs/current/adt-manual/adt-manual.html#optionally-building-a-toolchain-installer

[Michal_Pawlowski]

Brendan Le Foll (Intel) wrote:

Quote:

Michal P. wrote:

I read that part of yocto documentation that touches on development environment. My understanding is that I need to build image and dev tools using bitbake, is that correct?

Correct, we build our is SDK with "bitbake -c populate_sdk iot-devkit-prof-dev-image" and that gives you a large .sh which I believe you can install. See the documentation section 2.4.

http://www.yoctoproject.org/docs/current/adt-manual/adt-manual.html#opti...

It worked like a charm, thanks :)

[Michal_Pawlowski]

And I just been able to build my first cross platform executable for galileo from my ubuntu following http://www.yoctoproject.org/docs/current/adt-manual/adt-manual.html#using-the-command-line.

Thanks again for your help Brendan :)

Do you think that it may make sense to document my findings for myself and people new to yocto who would like to start coding for galileo? Or is this process going to change in a near feature making it useless in a few weeks?

[Brendan_L_Intel]

Michal Pawlowski wrote:

And I just been able to build my first cross platform executable for galileo from my ubuntu following http://www.yoctoproject.org/docs/current/adt-manual/adt-manual.html#usin....

Thanks again for your help Brendan :)

Do you think that it may make sense to document my findings for myself and people new to yocto who would like to start coding for galileo? Or is this process going to change in a near feature making it useless in a few weeks?

Normally we should have better doc explaining this type of stuff coming online soon, however if you want, you can make a new post with whatever you can I'll get an admin to sticky it.

The yocto build process should not change much, and if it does we can always modify your post :)

[Michal_Pawlowski]

Brendan Le Foll (Intel) wrote:

Normally we should have better doc explaining this type of stuff coming online soon, however if you want, you can make a new post with whatever you can I'll get an admin to sticky it.

The yocto build process should not change much, and if it does we can always modify your post :)

Sounds good. I'll document it in the next few days and post it here.

[Christopher_M_2]

Hi Michal,

If you do that write up, your gona make life too easy for me ?  hehe

And Brendan I caught all those links to the src and docs - oh and the hints build/conf/local.conf.

I promise I'll dive in and rt_m. You guys saved me so much time pointing me right where to go.

Wasn't like that back in kernel 1.3 to 2.0 days. They made you work for it...

Now watch..  I'll blow it all up and won't even get hello world working.

[Michal_Pawlowski]

Hi Chris,

Try this:

http://www.itsudo.com/galileo/2014/03/03/setting-up-development-environment-for-galileo.html

http://www.itsudo.com/galileo/yocto/ruby/2014/03/05/customizing-what-goes-onto-yocto-image.html

However it is not very detailed, you should be able to follow it. If you encounter problems, post a comment and I will extend problematic sections.

Best,

Michal

[Brendan_L_Intel]

FYI this doc got updated which should help anyone in the future!

http://software.intel.com/sites/default/files/managed/f1/49/building_yocto_and__ipks.pdf

[Michal_Pawlowski]

Brendan Le Foll (Intel) wrote:

FYI this doc got updated which should help anyone in the future!

http://software.intel.com/sites/default/files/managed/f1/49/building_yoc...

Just got screen installed via opkg. Priceless!

Thanks a lot Brendan

[dasan_r_]

i got these while building .. can anyone help me?

Pseudo is not present but is required, building this first before the main build
Loading cache: 100% |###########################################| ETA:  00:00:00
Loaded 1984 entries from dependency cache.

Build Configuration:
BB_VERSION        = "1.16.0"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "colibri-t20"
DISTRO            = "angstrom"
DISTRO_VERSION    = "v2014.05"
TUNE_FEATURES     = "armv7a vfp callconvention-hard cortexa9"
TARGET_FPU        = "vfp"
meta-angstrom     = "colibri:1007f6c32a1614c688872562a5859919781339fa"
meta-toradex      = "colibri:b278a4b9e4a0e9077c83c46094b6e2fe6868fd79"
meta-oe           
meta-efl          
meta-gpe          
meta-gnome        
meta-xfce         
meta-initramfs    
meta-systemd      
meta-multimedia   = "colibri:3871d4561464eedc6a9a83b2c682ec7d29682873"
meta-lxde         = "colibri:d452531cb7f809d6c539a837fd7141e5b2966b7a"
meta-browser      = "colibri:5d176cb405497e5c5823fa14dbae353a2e1e3730"
meta              = "colibri:ae9dbd0e1e26ba2b35cbd08ec731aee62adedc23"

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: Failed to fetch URL ftp://ftp.gnu.org/gnu/m4/m4-1.4.16.tar.gz, attempting MIRRORS if available
WARNING: Failed to fetch URL ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.69.tar.gz, attempting MIRRORS if available
WARNING: Failed to fetch URL ftp://ftp.gnu.org/gnu/libtool/libtool-2.4.2.tar.gz, attempting MIRRORS if available
WARNING: Failed to fetch URL ftp://ftp.gnu.org/gnu/automake/automake-1.12.3.tar.gz, attempting MIRRORS if available
ERROR: Fetcher failure: Fetch command failed with exit code 4, output:
2014-05-26 14:52:42 (0.00 B/s) - Data connection: Connection timed out; Control connection closed.
2014-05-26 14:53:46 (0.00 B/s) - Data connection: Connection timed out; Control connection closed.

ERROR: Function failed: Fetcher failure for URL: 'ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.69.tar.gz'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/hardcube-new/openemb/oe-core/build/out-eglibc/work/i686-linux/autoconf-native-2.69-r9/temp/log.do_fetch.11234
ERROR: Task 32 (virtual:native:/home/hardcube-new/openemb/oe-core/build/../stuff/openembedded-core/meta/recipes-devtools/autoconf/autoconf_2.69.bb, do_fetch) failed with exit code '1'
ERROR: Fetcher failure: Fetch command failed with exit code 4, output:
2014-05-26 14:52:42 (0.00 B/s) - Data connection: Connection timed out; Control connection closed.
2014-05-26 14:53:46 (0.00 B/s) - Data connection: Connection timed out; Control connection closed.

ERROR: Function failed: Fetcher failure for URL: 'ftp://ftp.gnu.org/gnu/m4/m4-1.4.16.tar.gz'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/hardcube-new/openemb/oe-core/build/out-eglibc/work/i686-linux/m4-native-1.4.16-r4/temp/log.do_fetch.11233
ERROR: Task 60 (/home/hardcube-new/openemb/oe-core/build/../stuff/openembedded-core/meta/recipes-devtools/m4/m4-native_1.4.16.bb, do_fetch) failed with exit code '1'
ERROR: Fetcher failure: Fetch command failed with exit code 4, output:
2014-05-26 14:52:42 (0.00 B/s) - Data connection: Connection timed out; Control connection closed.
2014-05-26 14:53:46 (0.00 B/s) - Data connection: Connection timed out; Control connection closed.

ERROR: Function failed: Fetcher failure for URL: 'ftp://ftp.gnu.org/gnu/libtool/libtool-2.4.2.tar.gz'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/hardcube-new/openemb/oe-core/build/out-eglibc/work/i686-linux/libtool-native-2.4.2-r5.0/temp/log.do_fetch.11236
ERROR: Task 46 (/home/hardcube-new/openemb/oe-core/build/../stuff/openembedded-core/meta/recipes-devtools/libtool/libtool-native_2.4.2.bb, do_fetch) failed with exit code '1'
ERROR: Fetcher failure: Fetch command failed with exit code 4, output:
2014-05-26 14:52:43 (0.00 B/s) - Data connection: Connection timed out; Control connection closed.
2014-05-26 14:53:47 (0.00 B/s) - Data connection: Connection timed out; Control connection closed.

ERROR: Function failed: Fetcher failure for URL: 'ftp://ftp.gnu.org/gnu/automake/automake-1.12.3.tar.gz'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/hardcube-new/openemb/oe-core/build/out-eglibc/work/i686-linux/automake-native-1.12.3-r1/temp/log.do_fetch.11235
ERROR: Task 39 (virtual:native:/home/hardcube-new/openemb/oe-core/build/../stuff/openembedded-core/meta/recipes-devtools/automake/automake_1.12.3.bb, do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 18 tasks of which 14 didn't need to be rerun and 4 failed.
Waiting for 0 running tasks to finish:

Summary: 4 tasks failed:
  virtual:native:/home/hardcube-new/openemb/oe-core/build/../stuff/openembedded-core/meta/recipes-devtools/autoconf/autoconf_2.69.bb, do_fetch
  /home/hardcube-new/openemb/oe-core/build/../stuff/openembedded-core/meta/recipes-devtools/m4/m4-native_1.4.16.bb, do_fetch
  /home/hardcube-new/openemb/oe-core/build/../stuff/openembedded-core/meta/recipes-devtools/libtool/libtool-native_2.4.2.bb, do_fetch
  virtual:native:/home/hardcube-new/openemb/oe-core/build/../stuff/openembedded-core/meta/recipes-devtools/automake/automake_1.12.3.bb, do_fetch
Summary: There were 4 WARNING messages shown.
Summary: There were 8 ERROR messages shown, returning a non-zero exit code.

[Brendan_L_Intel]

dasan r. wrote:

2014-05-26 14:52:43 (0.00 B/s) - Data connection: Connection timed out; Control connection closed.

Looks like your internet connection is not working. Maybe you're behind a proxy.