[yocto] extracting SDK for supporting both 32 and 64 bit applications

Dear community, I am using Freescale's SDK 1.8 based on poky 1.6.2. How can extract SDK that supports building of both 32 and 64 bit applications? I defined configuration for my board to be 32 bit with 64 bit kernel and extracted SDK for application development. Everything works fine: I can

Re: [yocto] [meta-raspberrypi] du giving non-integer result?

I saw such behavior in 'expr' when I upgraded bash 3.1 - it started printing floats instead of integers. You can solve it using awk's OFMT: awk '{OFMT="%.0f";print $1}' Michael -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of

Re: [yocto] Compile on recipe works the second time

See below Michael -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto- boun...@yoctoproject.org] On Behalf Of Bryan Evenson Sent: יום ג 19 נובמבר 2013 18:19 To: Paul Eggleton Cc: yocto@yoctoproject.org Subject: Re: [yocto] Compile on recipe works the second

[yocto] MACHINE setting

Hi, I have several similar boards with different PPC CPUs. How can I build packages for different MACHINEs without changing local.conf? I tried setting MACHINE and/or MACHINEOVERRIDES in my recipe that lists all my other recipes in DEPENDS. However, MACHINE setting affected only the main

Re: [yocto] do_clean failure on NFS drive

-Original Message- From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com] Sent: יום ד 24 אפריל 2013 13:13 To: Michael Fainstein Cc: yocto@yoctoproject.org Subject: Re: [yocto] do_clean failure on NFS drive On Tuesday 23 April 2013 06:10:05 Michael Fainstein wrote: Recently I

[yocto] do_clean failure on NFS drive

Recently I moved my working environment from local drive to NFS and since then do_clean task is failing all the time with error: ERROR: Error executing a python function in ..: OSError: [Errno 39] Directory not empty: '../temp' However, when I look at temp directory it is empty! I put

[yocto] strip path in meta/site/common-linux

IMHO program strip should be removed from meta/site/common-linux. I had a problem in my recipe: 'make install' was failing due to /usr/bin/strip failure to recognize file format (I am building for powerpc on x86_64 PC). I traced this error back to ./configure that was selecting /usr/bin/strip

[yocto] how to use native executable from one recipe during install in another recipe

I have one recipe that inherits native, builds native executable and installs it in tmp/work/x86_64-linux/foo-native-1.00-r0/image/sbin/foo Another recipe depends on first one and needs to execute foo in its do_install in order to install files in

Re: [yocto] how to use native executable from one recipe during install in another recipe

-Original Message- From: Eric Bénard [mailto:e...@eukrea.com] Sent: יום ה 11 אפריל 2013 15:53 To: Michael Fainstein Cc: yocto@yoctoproject.org Subject: Re: [yocto] how to use native executable from one recipe during install in another recipe Hi Michael, Le Thu, 11 Apr 2013 11

Re: [yocto] how to convert source rpm spec to bitbake recipe?

-Original Message- From: Samuel Stirtzel [mailto:s.stirt...@googlemail.com] Sent: יום ד 03 אפריל 2013 13:47 To: Paul Eggleton Cc: Michael Fainstein; yocto@yoctoproject.org Subject: Re: [yocto] how to convert source rpm spec to bitbake recipe? 2013/4/3 Paul Eggleton paul.eggle

[yocto] how to convert source rpm spec to bitbake recipe?

Is there a tool or guide for conversion of source rpm spec file to bitbake recipe? I have a distro for our embedded product based on CentOS 5 with about 140 packages. Third are source rpm packages from CentOS without any change, third are with some of our proprietary changes and the