Re: [yocto] raspberry pi do rootfs

Hi All, I have 60GB space in my build system still i face NOTE: Preparing RunQueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: Error: The image creation script '/home/raj/Projects/raspberry_pi/yacto/poky/raspberrypi_build/tmp/work/raspberrypi-poky-linux-gnueabi/rpi-hwup-

[yocto] external-toolchain

Hi, to start with yoctoproject for my new developed hardware, i would like to use my own crosstool-NG. Instead of this, i use YP Core - Dizzy 1.7.3 build-system and to simplify i am using the sourcery-toolchain layer(meta-sourcery-master). But now i had to recognize that the versions are not compa

Re: [yocto] external-toolchain

  ok i solved it by change TARGET_VENDOR = "-e500v2" in poky.conf.   thanks         Gesendet: Mittwoch, 11. November 2015 um 09:46 Uhr Von: "Virgilia Eigner" An: yocto@yoctoproject.org Betreff: [yocto] external-toolchain Hi, to start with yoctoproject for my new developed hardware, i

Re: [yocto] raspberry pi do rootfs

-- Andrei Gherzan On Wed, Nov 11, 2015 at 9:09 AM, Raj Jar wrote: > Hi All, > > I have 60GB space in my build system still i face > > Do you have any custom modifications or so. It seems like the fat partition is not big enough for what you write in. What poky/meta-rpi are you using? > > NOTE:

Re: [yocto] raspberry pi do rootfs

cts/raspberry_pi/yacto/poky/meta-raspberrypi/recipes-core/images/ > rpi-hwup-image.bb, do_rootfs > Summary: There were 2 ERROR messages shown, returning a non-zero exit code. > > > > -- Regards, RAJ M Mob. # +91-9597208150 Have a great day ahead. -- next part

Re: [yocto] Transitioning to Yocto, some basic questions about workflow

On 10 November 2015 at 22:27, Michael Habibi wrote: > I see that Yocto thinks of the deployable image and applications as > separate entities: first you'd build the distribution, then you would use > ADT/cross-toolchain/etc to build the applications and install them > separately. However, in our

Re: [yocto] Transitioning to Yocto, some basic questions about workflow

Randy, I've had some time to think about your post and I had a follow up question. Let's say we had internal applications, you suggest that the fetcher can be used to pull down the git/svn repos that contains the internal application code. In this environment, where is the Yocto framework hosted? I

Re: [yocto] Run-time discovery of machine for image compatibility check

The recommendations on your blog suggest modifying image-buildinfo.bbclass to change IMAGE_BUILDINFO_VARS. You /should/ be able to avoid this by simply adding something like IMAGE_BUILDINFO_VARS_append = " MACHINE DEVICE_MODEL DEVICE_TYPE" or IMAGE_BUILDINFO_VARS = "DISTRO DISTRO_VERSION MACHINE

Re: [yocto] Transitioning to Yocto, some basic questions about workflow

On Wed, Nov 11, 2015 at 7:36 AM, Michael Habibi wrote: > Randy, I've had some time to think about your post and I had a follow up > question. Let's say we had internal applications, you suggest that the > fetcher can be used to pull down the git/svn repos that contains the > internal application c

Re: [yocto] [PATCH 03/10][AUH] recipe.py: Improvements and refactor of fetch method.

Hi Paul, On 11/10/2015 02:46 AM, Paul Eggleton wrote: > Hi Aníbal, > > On Monday 09 November 2015 16:01:34 Aníbal Limón wrote: >> Make more clear fetch method changing recursive manner to >> loop and split logic into try fetch and suffix change. >> >> Now when fails only retry changing recipe su

Re: [yocto] [PATCH 04/10][AUH] buildhistory.py: Don't modify BB_ENV_EXTRAWHITE before init.

On 11/10/2015 02:54 AM, Paul Eggleton wrote: > On Monday 09 November 2015 16:01:35 Aníbal Limón wrote: >> Move code for add BUILDHISTORY_DIR to __init__ method because >> it fails when import in early step. >> >> Signed-off-by: Aníbal Limón >> --- >> buildhistory.py | 5 ++--- >> 1 file changed

Re: [yocto] [PATCH 05/10][AUH] upgradehelper.py: Add sanity test for ensure that git is configured.

On 11/10/2015 02:59 AM, Paul Eggleton wrote: > On Monday 09 November 2015 16:01:36 Aníbal Limón wrote: >> [YOCTO #8390] >> >> Signed-off-by: Aníbal Limón --- >> upgradehelper.py | 16 +++- 1 file changed, 11 >> insertions(+), 5 deletions(-) >> >> diff --git a/upgradehelper.py b/upg

Re: [yocto] [PATCH 08/10][AUH] upgradehelper.py: Add support for do recipe upgrades based on builddep

Sure. I forget it :). On 11/10/2015 03:09 AM, Paul Eggleton wrote: > On Monday 09 November 2015 16:01:39 Aníbal Limón wrote: >> Signed-off-by: Aníbal Limón >> --- > > Please provide a proper commit message for this one. > > Cheers, > Paul > -- ___ y

[yocto] [[AUH] PATCHv2 01/13] upgradehelper.py: Add step for build gcc-runtime at init.

When try to upgrade a recipe the first recipe in the list takes too much time because gcc-runtime build is needed. So add previous step to build gcc-runtime for every machine. Signed-off-by: Aníbal Limón --- upgradehelper.py | 5 + 1 file changed, 5 insertions(+) diff --git a/upgradehelper

[yocto] [[AUH] PATCHv2 00/13] Improvements and small fixes

This changeset fixes comments made by Paul Eggleton and adds 3 new commits the last ones related to send email improvements. The changes can be found at, http://git.yoctoproject.org/cgit/cgit.cgi/auto-upgrade-helper/log/?h=devel Aníbal Limón (13): upgradehelper.py: Add step for build gcc-runti

[yocto] [[AUH] PATCHv2 02/13] upgradehelper.py: Fix bug when buildhistory isn't enabled

Don't use buildhistory object if buildhistory_enabled is False because cause undefined variable error. Signed-off-by: Aníbal Limón --- upgradehelper.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/upgradehelper.py b/upgradehelper.py index bb19b65..9b321f6 100755 --- a/upgr

[yocto] [[AUH] PATCHv2 05/13] upgradehelper.py: Add sanity test for ensure that git is configured.

[YOCTO #8390] Signed-off-by: Aníbal Limón --- upgradehelper.py | 16 +++- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index 9b321f6..195d8c9 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -28,6 +28,7 @@ import argpars

[yocto] [[AUH] PATCHv2 06/13] buildhistory.py: Add missing warning import. git.py: Fix last_commit method.

Signed-off-by: Aníbal Limón --- buildhistory.py | 3 ++- git.py | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/buildhistory.py b/buildhistory.py index 59566c8..842efc3 100644 --- a/buildhistory.py +++ b/buildhistory.py @@ -20,8 +20,9 @@ import os import loggin

[yocto] [[AUH] PATCHv2 03/13] recipe.py: Improvements and refactor of fetch method.

Make more clear fetch method changing recursive manner to loop and split logic into try fetch and suffix change. Now when fails only retry changing recipe suffix when recipe isn't git based because does not make sense suffixes in SCM's. Signed-off-by: Aníbal Limón --- recipe.py | 58 +++

[yocto] [[AUH] PATCHv2 04/13] buildhistory.py: Don't modify BB_ENV_EXTRAWHITE before init.

Move code for add BUILDHISTORY_DIR to __init__ method because it fails when import in early step. Signed-off-by: Aníbal Limón --- buildhistory.py | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/buildhistory.py b/buildhistory.py index 1732f23..59566c8 100644 --- a/buildhi

[yocto] [[AUH] PATCHv2 07/13] upgradehelper.py: Improve work directory structure

Add work directory with datetime suffix to preserve recipe upgrades. Create tree folders all, succeed and failed, all - Contains all the recipes work succeed - Contains a symlinks to the recipes that successful upgrade failed - Contains a symlinks to

[yocto] [[AUH] PATCHv2 08/13] upgradehelper.py: Add support for do recipe upgrades based on builddep

Now upgradehelper runs recipe upgrades based on build dependencies, the dependency information is taken of bitbake dependency graph. So if recipe a depends in build time on recipe b and c these recipes b and c are first tried to upgrade then a. Signed-off-by: Aníbal Limón --- upgradehelper.py |

[yocto] [[AUH] PATCHv2 09/13] upgradehelper.py: Add support for preserve statistics into work directory.

Signed-off-by: Aníbal Limón --- upgradehelper.py | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/upgradehelper.py b/upgradehelper.py index 5bb066a..a3ca373 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -591,7 +591,16 @@ class Updater(object):

[yocto] [[AUH] PATCHv2 10/13] requirements.txt: Add file for now only with GitPython

Signed-off-by: Aníbal Limón --- requirements.txt | 1 + 1 file changed, 1 insertion(+) create mode 100644 requirements.txt diff --git a/requirements.txt b/requirements.txt new file mode 100644 index 000..64b1ada --- /dev/null +++ b/requirements.txt @@ -0,0 +1 @@ +GitPython -- 2.1.4 -- __

[yocto] [[AUH] PATCHv2 13/13] upgradehelper.py: Add support for preserve emails.

This support is useful for review purposes after upgrade process and these emails are saved into recipe work directory. Signed-off-by: Aníbal Limón --- upgradehelper.py | 14 ++ 1 file changed, 14 insertions(+) diff --git a/upgradehelper.py b/upgradehelper.py index f7ce425..5eb9f5a

[yocto] [[AUH] PATCHv2 11/13] upgradehelper.py: Only send email to Maintainer when upgrade succeed.

Change the policy for send emails to only send when upgrade succeed to avoid waste time of the Maintainers when upgrade process fails because the failure patch generated isn't useful. Signed-off-by: Aníbal Limón --- upgradehelper.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

[yocto] [[AUH] PATCHv2 12/13] upgradehelper.py: Fix indent due to previous commit.

Signed-off-by: Aníbal Limón --- upgradehelper.py | 109 +++ 1 file changed, 53 insertions(+), 56 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index c2bf506..f7ce425 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -353,6

Re: [yocto] raspberry pi do rootfs

/raspberrypi_build/tmp/work/raspberrypi-poky-linux-gnueabi/rpi-hwup-image/1.0-r0/temp/log.do_rootfs.13457 > > ERROR: Task 7 > > > (/home/raj/Projects/raspberry_pi/yacto/poky/meta-raspberrypi/recipes-core/images/ > > rpi-hwup-image.bb, do_rootfs) failed with exit code '1' >