Re: [yocto] Error do_compile libepoxy

On 01/18/2018 10:58 AM, Andrea Galbusera wrote: Looks like my first guess was not that bad. Reverting below commit, which switched to meson build system brought my build back to green. Also CC-ing the patch author who might suggest further investigations. libepoxy: convert to meson build

Re: [yocto] Postinstallation script warnings in Yocto 2.4 Rocko

On 01/17/2018 07:10 PM, Diaz de Grenu, Jose wrote: The patches work, but I was wondering if we really need to mark this behavior as a WARNING. From my point of view, this may be confusing for a user, as it could lead to think that something is wrong. But I think that, even if image post proce

[yocto] [auh 1/2] weeklyjob.sh: use -e with auh to actually send the emails

Signed-off-by: Alexander Kanavin --- weeklyjob.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/weeklyjob.sh b/weeklyjob.sh index ac50461..2e8c434 100755 --- a/weeklyjob.sh +++ b/weeklyjob.sh @@ -20,7 +20,7 @@ git fetch origin git checkout -B tmp-auh-upgrades origin/master

[yocto] [auh 2/2] upgradehelper.py: add a reference to License-Update: tag.

Signed-off-by: Alexander Kanavin --- upgradehelper.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/upgradehelper.py b/upgradehelper.py index 1170ca5..b22b915 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -276,7 +276,9 @@ class Updater(object

Re: [yocto] [Pyro] Multiple toolchains

On 01/17/2018 05:59 PM, philippe gislard wrote: We are updating our BSP from Krogoth to Pyro. We are using a kernel designed and patched specifically for our hardware (3.10.40) that does not compile with GCC 5.x or GCC6.x. AFAIK, Pyro is qualified with GCC 5.x and GCC6.x (not with earlier version

Re: [yocto] Backport of oe-core patch 147074 to rocko

On 01/16/2018 04:32 PM, Jan Siegmund wrote: could commit 953f6d9a717945cc20228e7f75371adc27f4ffbe be added to branch rocko? It fixes breaking packaging when using lz4. Certainly; prepare a patch, and send it to oe-core list with [rocko] prefix. Alex -- _

Re: [yocto] [OE-core] liblzma: Memory allocation failed on do_package_rpm

On 01/15/2018 08:20 AM, Manjukumar Harthikote Matha wrote: All, Has anybody seen this error? Finished binary package job, result 0, filename (null) error: create archive failed: cpio: write failed - Cannot allocate memory error: liblzma: Memory allocation failederror: liblzma: Memory allocation

Re: [yocto] rdepends = "python3-modules" in recipe does not install python3-modules in image

On 01/09/2018 08:45 PM, Matt Schepers wrote: For this recipe the base package is called users.rpm and I can see it in the RPM. Using 'bitbake users -e | grep PN' I was able to find that PN is also set to users, which seems correct. However the recipe does not install python3-modules even thoug

Re: [yocto] Upgrading Yocto Project Version - To Rocko

On 01/09/2018 01:55 PM, Kok, Vincent Chin Keong wrote: I was wondering, how can I upgrade to Yocto version 2.4 (Rocko)? Do I just remove the previous poky folder I downloaded and re-download a newer version of poky and checkout the branch and tags? The easiest is to perform a clean clone of t

Re: [yocto] Postinstallation script warnings in Yocto 2.4 Rocko

On 01/08/2018 02:31 PM, Martin Hundebøll wrote: On 2018-01-08 13:19, Alexander Kanavin wrote: The problem is that in Yocto 2.4 then any build which requires on-target postinstallation script is going to trigger warning, even if it is completely correct. Is there no way around this? Is there a

Re: [yocto] Postinstallation script warnings in Yocto 2.4 Rocko

On 01/08/2018 01:44 PM, Diaz de Grenu, Jose wrote: Thanks for the information. I guess this fix will be for Yocto 2.5? Maybe; I'm working right now on the patchset, and will post it to oe-core list later today. Last time it was a bit controversial, so I'd appreciate if you a) try and test it;

Re: [yocto] Postinstallation script warnings in Yocto 2.4 Rocko

On 01/08/2018 11:14 AM, Diaz de Grenu, Jose wrote: I am trying to create a recipe with a post installation script. I am using the following fragment of code (as documented in http://www.yoctoproject.org/docs/2.4/mega-manual/mega-manual.html#new-recipe-post-installation-scripts ): pkg_postins

Re: [yocto] rdepends = "python3-modules" in recipe does not install python3-modules in image

On 01/06/2018 08:00 PM, Matt Schepers wrote: How do I check what PN is set to? I can see users-dbg.rpm and users-doc.rpm in the rpm folder. The recipe name is users.bb If the recipe is named users, then PN is most likely users as well. -doc and -dbg are supplementary packages. What is the main

Re: [yocto] rdepends = "python3-modules" in recipe does not install python3-modules in image

On 01/05/2018 06:41 PM, Matt Schepers wrote: This does not install "python3-modules" to the image. When this builds, my python program does not work because of missing dependencies on the standard library. To get this to work I have to go in and append "python3-modules" to IMAGE_INSTALL in my

Re: [yocto] Smart Project Manager

On 01/05/2018 05:06 PM, Kirill Kondrashov wrote: Thanks for advice, but at the moment it's a bit of a problem, I'm stuck with poky2.0.3 bound to a specific board, so I will keep up with smart. But what's the benefit of dnf? Talk to the provider of the BSP layer, and ask why you need to be stuc

Re: [yocto] Smart Project Manager

On 12/28/2017 01:37 PM, Kirill Kondrashov wrote: Is there some existing C/C++ API for smart pm? I have to interface it from Qt software and wonder if there's some other way rather then just intercepting python scripts output. Upgrade to a recent yocto release, which has replaced dnf with smart

[yocto] [auh][PATCH 21/21] testimage.py: collect and write out logs from bitbake and testimage

Signed-off-by: Alexander Kanavin --- modules/testimage.py | 31 +++ 1 file changed, 27 insertions(+), 4 deletions(-) diff --git a/modules/testimage.py b/modules/testimage.py index 699d619..35e23c9 100644 --- a/modules/testimage.py +++ b/modules/testimage.py @@ -49,8

[yocto] [auh][PATCH 20/21] testimage.py: rewrite the logic for building and running testimages

; this is prone to mistmatches and is best left to a human. Signed-off-by: Alexander Kanavin --- modules/testimage.py | 115 +-- 1 file changed, 10 insertions(+), 105 deletions(-) diff --git a/modules/testimage.py b/modules/testimage.py index

[yocto] [auh][PATCH 19/21] testimage.py: remove all iterations (over machines, over failing recipes)

o the standard integration testimage. Signed-off-by: Alexander Kanavin --- README | 9 +++-- modules/testimage.py | 107 ++- 2 files changed, 9 insertions(+), 107 deletions(-) diff --git a/README b/README index acb22ac..84e140f 1

[yocto] [auh][PATCH 18/21] testimage.py: run even if no packages were upgraded

Signed-off-by: Alexander Kanavin --- modules/testimage.py | 4 1 file changed, 4 deletions(-) diff --git a/modules/testimage.py b/modules/testimage.py index 86e817c..1195916 100644 --- a/modules/testimage.py +++ b/modules/testimage.py @@ -256,10 +256,6 @@ class TestImage(): return

[yocto] [auh][PATCH 17/21] testimage.py: clarify what arguments are passed to class constructor

Signed-off-by: Alexander Kanavin --- modules/testimage.py | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/modules/testimage.py b/modules/testimage.py index 6c4ed2b..86e817c 100644 --- a/modules/testimage.py +++ b/modules/testimage.py @@ -1,4 +1,3 @@ -#!/usr/bin/env

[yocto] [auh][PATCH 16/21] upgradehelper.py: do not include testimage information in maintainer email messages

Signed-off-by: Alexander Kanavin --- upgradehelper.py | 23 --- 1 file changed, 23 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index 5659735..1170ca5 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -290,17 +290,6 @@ class Updater(object):

[yocto] [auh][PATCH 14/21] upgradehelper.py: do not include absolute paths in the generated tarball

Signed-off-by: Alexander Kanavin --- upgradehelper.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/upgradehelper.py b/upgradehelper.py index 9110efc..cb48c47 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -555,9 +555,11 @@ class Updater(object

[yocto] [auh][PATCH 15/21] Do not require configuration options that aren't necessary for running ptests

Signed-off-by: Alexander Kanavin --- README | 6 ++ upgradehelper.py | 15 --- 2 files changed, 2 insertions(+), 19 deletions(-) diff --git a/README b/README index 27b0977..acb22ac 100644 --- a/README +++ b/README @@ -122,10 +122,8 @@ file: --- snip

[yocto] [auh][PATCH 13/21] Add protection measures and information against running with existing build directories.

This should help e.g. with the following issue: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7174 Signed-off-by: Alexander Kanavin --- README | 12 upgradehelper.py | 14 ++ weeklyjob.sh | 2 +- 3 files changed, 23 insertions(+), 5 deletions(-) diff

[yocto] [auh][PATCH 12/21] Add support for compiling against non-default C libraries

Particularly, musl is a notorious source of failures and so it's very useful to do at least one build against it by default. Signed-off-by: Alexander Kanavin --- README | 4 +++- modules/utils/bitbake.py | 7 ++- upgradehelper.py | 2 +- 3 files change

[yocto] [auh][PATCH 11/21] weeklyjob.sh: set up a temporary branch and clean up afterwards

Signed-off-by: Alexander Kanavin --- weeklyjob.sh | 14 +- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/weeklyjob.sh b/weeklyjob.sh index e2c4b1a..8dd0a1c 100755 --- a/weeklyjob.sh +++ b/weeklyjob.sh @@ -7,11 +7,23 @@ # # 00 8 * * 6 auh /home/auh/bin

[yocto] [auh][PATCH 10/21] upgradehelper.py: replace the confusing 'maintainer' command line option

It wasn't clear what the option does, and why it need to be on the command line, so the replacement is a 'global_maintainer_override' config file setting which does the same thing, in a cleaner fashion. Signed-off-by: Alexander Kanavin --- README | 7 ++- upgra

[yocto] [auh][PATCH 09/21] upgradehelper.py: drop automatic mode

No longer used since migration to devtool: all upgrades are automatic Signed-off-by: Alexander Kanavin --- README | 6 ++ upgradehelper.py | 6 +- 2 files changed, 3 insertions(+), 9 deletions(-) diff --git a/README b/README index 60dbef9..00a390a 100644 --- a/README +++ b

[yocto] [auh][PATCH 08/21] upgradehelper.py: don't build gcc-runtime when --skip-compilation

From: Robert Yang It doesn't make any sense to build it when skip compile. Signed-off-by: Robert Yang --- upgradehelper.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/upgradehelper.py b/upgradehelper.py index 80ea4f4..711d3b3 100755 --- a/upgradehelper.py +++ b/upgradeh

[yocto] [auh][PATCH 07/21] upgradehelper.py: print info when recipe is skipped to upgrade

From: Robert Yang This makes debug easier. Signed-off-by: Robert Yang --- upgradehelper.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index 3c40918..80ea4f4 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -691,11 +691,11

[yocto] [auh][PATCH 06/21] upgradehelper.py: always do upgrade when recipes are specified

From: Robert Yang For example, first run: $ upgradehelper.py less -d 5 It did the upgrade Second run: $ upgradehelper.py less -d 5 DEBUG: Skipping upgrade of less: is in history and not 30 days passed Let it always do the upgrade makes it easier to use when do upgrade locally. It will still do

[yocto] [auh][PATCH 04/21] modules/steps.py: fix warn when skip compilation

From: Robert Yang Signed-off-by: Robert Yang --- modules/steps.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/steps.py b/modules/steps.py index 63f43c8..5bbe38e 100644 --- a/modules/steps.py +++ b/modules/steps.py @@ -113,7 +113,7 @@ def _compile(bb, pkg, machine

[yocto] [auh][PATCH 05/21] upgradehelper.py: only check email settings when -e is specified

From: Robert Yang Fixed: $ upgradehelper.py less ERROR: smtp host not set! Sending emails disabled! ERROR: 'From' address not set! Sending emails disabled! Only check email settings when "-e" is specified can fix the problem. Signed-off-by: Robert Yang --- upgradehelper.py | 3 ++- 1 file cha

[yocto] [auh][PATCH 03/21] upgradehelper.py: use UniverseUpdater for all cases

From: Robert Yang * Use UniverseUpdater() for the following 3 cases: + Upgrade all recipes + Upgrade 1 recipe - '--maintainer' is not a must when any more when use --send-emails, the maintainer be got from distrodata. + Upgrade multiple recipes * Use "args" as the parameter of Un

[yocto] [auh][PATCH 02/21] upgradehelper.py: support upgrade multiple recipes

From: Robert Yang Now we can use: $ upgradehelper.py recipe1 recipe2 Signed-off-by: Robert Yang --- upgradehelper.py | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index 4797fd8..c81e748 100755 --- a/upgradehelper.py +++ b/upgra

[yocto] [auh][PATCH 01/21] upgradehelper.py: fix checking for do_checkpkg

From: Robert Yang The error message in the log is: Initialising tasks...ERROR: Task do_checkpkg does not exist for target strace [snip] So line.find("ERROR: Task do_checkpkg does not exist") == 0 doesn't work, use != -1 to fix the problem. Signed-off-by: Robert Yang --- upgradehelper.py | 2

[yocto] [auh][PATCH 00/21] Further enhancements to automatic upgrade helper

ommit fbccfa00967305bb3866d0f610cd4b83b8b7a28c: upgradehelper.py: revert commits that failed to build (2017-12-14 18:13:11 +0200) are available in the Git repository at: git://git.yoctoproject.org/auto-upgrade-helper devel http://git.yoctoproject.org/cgit.cgi/auto-upgrade-helper/log/?h=devel Alexander Kanavi

Re: [yocto] [PATCH 08/12] upgradehelper.py: clean repo only once when recipes are specified

On 12/14/2017 06:38 PM, Alexander Kanavin wrote: Got it, thanks. I just sent the patches to yocto@ ML and published them on github - please do try them out, and rebase your patchset on top (some of it may no longer be relevant). I did the rebase myself, and pushed the result here - please

Re: [yocto] [PATCH 08/12] upgradehelper.py: clean repo only once when recipes are specified

On 12/14/2017 04:13 AM, Robert Yang wrote: How about simply issuing 'git revert' after a build has failed? That's easier to implement than rearranging the order of commits, and the commit message can include a link to the build failure logs. Sounds reasonable to me, I will update the patch.

[yocto] [auh][PATCH 20/20] upgradehelper.py: revert commits that failed to build

From: Alexander Kanavin This helps avoid 'cascading build failures' where one failed update holds up everything else. Signed-off-by: Alexander Kanavin --- modules/utils/git.py | 3 +++ upgradehelper.py | 3 +++ 2 files changed, 6 insertions(+) diff --git a/modules/utils/git.py

[yocto] [auh][PATCH 19/20] upgradehelper.py: when recovering from upgrade error, do not refer to a dict entry that may not exist

From: Alexander Kanavin Signed-off-by: Alexander Kanavin --- upgradehelper.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/upgradehelper.py b/upgradehelper.py index 3c41012..58fa0a6 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -510,7 +510,7 @@ class Updater

[yocto] [auh][PATCH 18/20] upgradehelper.py: when attempting to commit changes do not discard previous errors

From: Alexander Kanavin Signed-off-by: Alexander Kanavin --- upgradehelper.py | 11 ++- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index d1f441c..3c41012 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -397,7 +397,6

[yocto] [auh][PATCH 17/20] upgradehelper.py: add all changes before committing them

From: Alexander Kanavin Signed-off-by: Alexander Kanavin --- modules/utils/git.py | 3 +++ upgradehelper.py | 1 + 2 files changed, 4 insertions(+) diff --git a/modules/utils/git.py b/modules/utils/git.py index a6f5422..0e812b9 100644 --- a/modules/utils/git.py +++ b/modules/utils/git.py

[yocto] [auh][PATCH 16/20] upgradehelper.py: send email even if recipe upgrade failed

From: Alexander Kanavin Signed-off-by: Alexander Kanavin --- upgradehelper.py | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index d3cc2c4..043d334 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -380,8 +380,7 @@ class Updater

[yocto] [auh][PATCH 15/20] upgradehelper.py: fixups to the email message template

From: Alexander Kanavin Signed-off-by: Alexander Kanavin --- upgradehelper.py | 43 +++ 1 file changed, 27 insertions(+), 16 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index d62c9b2..d3cc2c4 100755 --- a/upgradehelper.py +++ b

[yocto] [auh][PATCH 10/20] modules/recipe: remove

From: Alexander Kanavin The hand-crafted recipe updating/rewriting has been replaced by calling devtool. Signed-off-by: Alexander Kanavin --- modules/recipe/__init__.py | 0 modules/recipe/base.py | 724 - modules/recipe/git.py | 98

[yocto] [auh][PATCH 14/20] testimage.py: add extra logging for the testimage logs retrieval

From: Alexander Kanavin This helped with diagnozing issues described in https://bugzilla.yoctoproject.org/show_bug.cgi?id=12396 Signed-off-by: Alexander Kanavin --- modules/testimage.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/modules/testimage.py b/modules/testimage.py index

[yocto] [auh][PATCH 13/20] testimage.py: do not call into removed code

From: Alexander Kanavin This was using the removed recipe parsing code to determine if a package supports ptest; it should be replaced with using bitbake API but for now we can simply add all update packages to the list. Signed-off-by: Alexander Kanavin --- modules/testimage.py | 12

[yocto] [auh][PATCH 11/20] upgradehelper.py: remove the package ordering code

From: Alexander Kanavin It was broken and commented out, and not really necessary. Signed-off-by: Alexander Kanavin --- upgradehelper.py | 80 1 file changed, 80 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index

[yocto] [auh][PATCH 12/20] utils/git.py: print current dir when git fails

From: Alexander Kanavin Signed-off-by: Alexander Kanavin --- modules/utils/git.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/utils/git.py b/modules/utils/git.py index d1fe41b..a6f5422 100644 --- a/modules/utils/git.py +++ b/modules/utils/git.py @@ -40,7 +40,7

[yocto] [auh][PATCH 09/20] Replace references to Aníbal Limón as the maintainer.

From: Alexander Kanavin Signed-off-by: Alexander Kanavin --- README | 2 +- upgradehelper.py | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README b/README index e6b0dc2..60dbef9 100644 --- a/README +++ b/README @@ -163,7 +163,7 @@ The latest version of the

[yocto] [auh][PATCH 08/20] testimage.py: do not manipulate branches

From: Alexander Kanavin AUH simply creates a series of commits now, so we can create and run testimage directly on the branch we're on. Signed-off-by: Alexander Kanavin --- modules/testimage.py | 32 1 file changed, 32 deletions(-) diff --git a/mo

[yocto] [auh][PATCH 07/20] buildhistory.py: replace cleanall with cleansstate

From: Alexander Kanavin It should not be really necessary, and wastes time as the upstream source needs to be re-fetched. Signed-off-by: Alexander Kanavin --- modules/buildhistory.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/buildhistory.py b/modules

[yocto] [auh][PATCH 06/20] Add devtool support for upgrading recipes

From: Alexander Kanavin devtool has a much better support for rebasing patches, can be used interactively when things go wrong, and we also need to avoid having two codebases for updating recipes that broadly do the same thing. Signed-off-by: Alexander Kanavin --- modules/errors.py

[yocto] [auh][PATCH 05/20] upgradehelper.py: add the old recipe version in pkg_ctx

From: Alexander Kanavin So that it can be later used in the commit message. Signed-off-by: Alexander Kanavin --- upgradehelper.py | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index c11993a..9a59941 100755 --- a

[yocto] [auh][PATCH 04/20] upgradehelper.py: support updates to a new vcs revision.

From: Alexander Kanavin Devtool has support for this, and it's useful when the upstream never issues new versions; in this situation we can simply attempt to update to the latest revision. Signed-off-by: Alexander Kanavin --- upgradehelper.py | 10 ++ 1 file changed, 6 inser

[yocto] [auh][PATCH 03/20] upgradehelper.py: do not manipulate git branches.

From: Alexander Kanavin Let's just write the commits into the current branch, and leave branch management to some other tool. Signed-off-by: Alexander Kanavin --- upgradehelper.py | 25 - 1 file changed, 25 deletions(-) diff --git a/upgradehelper.py b/upgradehelp

[yocto] [auh][PATCH 02/20] upgradehelper.py: always run checkpkg

From: Alexander Kanavin There was code to skip upstream version check if it was performed recently, which was actually broken as it didn't verify that checkpkg.csv already contains the package we want to update. Let's just drop the whole logic and run checkpkg always. Signed-off-by:

[yocto] [auh][PATCH 00/20] Porting AUH to devtool and making it suitable for local use

mode do a full cleanup of poky (2017-06-05 16:14:23 -0500) are available in the Git repository at: git://github.com/kanavin/auh-devtool devel https://github.com/kanavin/auh-devtool/tree/devel Alexander Kanavin (20): upgradehelper.py: do not error out if testimage or buildhistory are

[yocto] [auh][PATCH 01/20] upgradehelper.py: do not error out if testimage or buildhistory are enabled in bitbake conf, but not in AUH conf

From: Alexander Kanavin Signed-off-by: Alexander Kanavin --- upgradehelper.py | 12 1 file changed, 12 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index 8e5466e..1356aef 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -240,12 +240,6 @@ class Updater

Re: [yocto] [PATCH 08/12] upgradehelper.py: clean repo only once when recipes are specified

On 12/13/2017 03:16 AM, Robert Yang wrote: How about simply issuing 'git revert' after a build has failed? That's easier to implement than rearranging the order of commits, and the commit message can include a link to the build failure logs. Sounds reasonable to me, I will update the patch.

Re: [yocto] [PATCH 08/12] upgradehelper.py: clean repo only once when recipes are specified

On 12/11/2017 08:13 AM, Robert Yang wrote: I think it's a simpler and easier to understand approach. Yes, this means that an updated recipe that is close to the root of dependency tree can cause a cascade of build failures (e.g. glibc), but the update commits for everything else will still be

Re: [yocto] recipe to clean up files from rootfs

On 12/11/2017 04:18 PM, Sherif Omran wrote: i want to create a recipe to clean some files from the rootfile system, but i don't know how to let this recipe run the last one before building the rootfile system. Have a look at ROOTFS_POSTPROCESS_COMMAND. Alex --

Re: [yocto] Checksum of an external file

On 12/11/2017 03:19 PM, Anton Gerasimov wrote: Unfortunately this doesn't work as expected (the recipe doesn't get rebuilt when the file changes, looks like calculate_file_sha256 doesn't run unless PATH_TO_FILE has changed) and at the same time if I 'cleanall' the recipe and change the file befor

Re: [yocto] [PATCH 08/12] upgradehelper.py: clean repo only once when recipes are specified

On 12/08/2017 04:00 AM, Robert Yang wrote: I'm not sure, the logical *without* this patch is: 1) Do the commit when succeed or failed. 2) git format-patch 3) Remove the commit if failed, and leave the commit there if succeed Sorry, "remove the comit if failed" is added by this patch, and why

Re: [yocto] [PATCH 09/12] upgradehelper.py: use git user in commit when recipes are specified

On 12/08/2017 03:51 AM, Robert Yang wrote: I'm not sure about this one. Commits shouldn't be created automatically on a person's behalf and then also signed-off - I'd say you need to first look at them. IMHO, Auh is a helper, when user run: $ auh less It helps create commits, should be the s

Re: [yocto] Preventing a variable from being cached

On 12/07/2017 10:30 PM, Paul Knopf wrote: Use a SRC_URI for another recip? Let me show you my recipe. SUMMARY = "Puts a file in the image that contains the application version." DESCRIPTION = "Puts a file in the image that contains the application version." Openembedded isn't really designed

Re: [yocto] Preventing a variable from being cached

On 12/07/2017 10:22 PM, Paul Knopf wrote: I have all my meta-layers and build conf files checked into a single repository (submodules for layers). I want a recipe to look at the git repository, and place a file in the build. I'd like this repository to read the HEAD, and decide if it needs to b

Re: [yocto] Good example of bbclass customization? maintainer

On 12/07/2017 07:08 PM, Marcelo E. Magallon wrote: My concern right now is a *different* case, where your goal is to modify the class in order to affect all the recipes already inheriting from it. For example, where there's a modification to a function in the class. Is there a good example out t

Re: [yocto] Preventing a variable from being cached

On 12/07/2017 05:47 PM, Paul Knopf wrote: I take it that this is not possible? A recipe will rebuild if you change SRCREV or SRC_URI in it. What are you trying to do? Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.

Re: [yocto] [PATCH 10/12] upgradehelper.py: add --apply-failed option

On 12/07/2017 09:37 AM, Robert Yang wrote: -f, --apply-failedApply failed patch in the repo after upgrade is done And add "FAILED:" in subject when failed. So that the user can go on working based on the commit. AUH will simple leave all commits in the repo, succeessful and failed. Eve

Re: [yocto] [PATCH 09/12] upgradehelper.py: use git user in commit when recipes are specified

On 12/07/2017 09:37 AM, Robert Yang wrote: E.g.,: $ upgradehelper.py less commit d9b551438037e105eebabbbcb2da6d8b8cae7504 Author: Robert Yang Date: Wed Dec 6 16:38:55 2017 +0800 less: upgrade to 529 Signed-off-by: Robert Yang I'm not sure about this one. Commits shouldn't be cr

Re: [yocto] [PATCH 08/12] upgradehelper.py: clean repo only once when recipes are specified

On 12/07/2017 09:37 AM, Robert Yang wrote: E.g.: $ upgradehelper.py less strace bash git The commit is removed when failed, and kept when succeed, but it would be removed when next recipe runs, so only run clean_repo once can keep the commit, which is helpful for the user. I have removed the l

Re: [yocto] [PATCH 05/12] modules/steps.py: fix warn when skip compilation

On 12/07/2017 09:37 AM, Robert Yang wrote: try: I(" %s: Upgrading to %s" % (pkg_ctx['PN'], pkg_ctx['NPV'])) for step, msg in upgrade_steps: +if step == compile and self.args.skip_compilation: +W(" %s: Sk

Re: [yocto] [PATCH 00/12] [auh] make it easy to use by recipe maintainer

On 12/07/2017 09:37 AM, Robert Yang wrote: Robert Yang (12): upgradehelper.py: fix checking for do_checkpkg upgradehelper.py: support upgrade multiple recipes upgradehelper.py: use UniverseUpdater for all cases modules/steps.py: fix warn when skip compilation modules/steps.py: fix

Re: [yocto] Allowing a local command to be executed in a recipe.

On 12/06/2017 07:55 PM, Paul Knopf wrote: I have a local utility that is manually installed on our dev/build machines. How do I configure Yocto to let me use this local command? It is located in /usr/local/bin. Lets say the command is "my-command". Write a recipe for the command, and inclu

Re: [yocto] externalsrc + sstate why is not compatible?

On 12/06/2017 04:13 PM, Koehler, Yannick wrote: When you say "subdirs", are you referring to submodules or something along those line? We have used attempted to use submodules and it still required 20 + 1 repo and the overhead is similar to yocto + 20 repo but then you have yocto + 20 repos +

Re: [yocto] variable override syntax, where is it documented?

On 12/06/2017 10:58 AM, Bernd wrote: I just found out that I can ovverride the line hostname = "${MACHINE}" in base-files simply by assigning a value to hostname_pn-base-files in my configuration file and it will re-assign it with a higher priority than "=". Now I wonder where this kind of b

Re: [yocto] externalsrc + sstate why is not compatible?

On 12/06/2017 04:15 AM, Koehler, Yannick wrote: In our situation, we have many packages that are in-house, as such we use a local folder for the several in-house modules. To do so, we need to use externalsrc to point to the local code so that the git repo contains both the code + recipe, instea

Re: [yocto] include and a library dependency in a recipe which uses a Makefile

On 12/01/2017 10:41 PM, Rail Shafigulin wrote: I need to use this Makefile in a recipe which but I'm struggling to figure out how to make it point to correct include folder as well as a library folder. While knowing how to do these things is useful, I think you should just drop the custom mak

Re: [yocto] dev package non-sym link

On 11/30/2017 11:46 PM, Rail Shafigulin wrote: do_install () { install -d ${D}${libdir}/ install -m 0755 ${S}/libAnokiWave.so.1.0.1 ${D}${libdir} ln -s ${D}${libdir}/libAnokiWave.so.1.0.1 ${D}${libdir}/libAnokiwave.so.1 ln -s ${D}${libdir}/libAnokiWave.so.1 ${D}${libdir}/libAnokiwave.

Re: [yocto] dev package non-sym link

On 11/30/2017 08:10 PM, Rail Shafigulin wrote: Somewhat new to Yocto. Trying to build a library. It compiled but I'm having issues during the package task. The error output is ERROR: anokiwavelib-1.0+gitAUTOINC+16df62468c-r0 do_package_qa: QA Issue: -dev package contains non-symlink .so: anokiwa

Re: [yocto] Invalidating tasks

On 11/29/2017 11:29 AM, Anton Gerasimov wrote: I've got two tasks, `do_A` and `do_B` (they are really IMAGE_CMDs if it's important). Now I want to introduce a third task, `do_check_A_and_B`, that will test that `do_A` and `do_B` have produced a correct result. If the test fails, I want to invalid

Re: [yocto] Executing ptest using image test ?

On 11/24/2017 04:30 PM, Koehler, Yannick wrote: I was not using -c testimage, and I also think the DISTRO_FEATURE may be incorrectly set in my case, I will try that, thanks for the pointer. Do read the comments in testimage.bbclass, as they explain how to use it. Particularly, seems like ptes

Re: [yocto] Executing ptest using image test ?

On 11/24/2017 03:59 PM, Koehler, Yannick wrote: I had pretty much done all that is documented under 4.21 of this documentation. I can execute my test within the image using "ptest_runner" and I see it PASS/FAIL according to my test's content. So that's great, but the problem with this is still

Re: [yocto] Executing ptest using image test ?

On 11/24/2017 04:07 AM, Koehler, Yannick wrote: I have some ptest which I would like to run quickly inside qemux86.  I see that the TEST_SUITES would allow me to do that, and that there is a _ptest.py script which seems to interface with ptest-runner.  Yet, I am unclear how it connects together

Re: [yocto] Generating Package/Image Developer Documentation

On 11/22/2017 06:16 PM, Koehler, Yannick wrote: I am using Yocto 1.9/2.0 and a quick grep doesn't seems to indicate support for this DISTRO_FEATURE. This was added about a year ago and Yocto 1.9 is a lot older. If you want to submit your work upstream, you have to rebase it to the master br

Re: [yocto] Generating Package/Image Developer Documentation

On 11/20/2017 09:53 PM, Koehler, Yannick wrote: The image would then install those documentation in the sysroot under some folder, maybe /usr/share/devdoc// and potentially create a tarball of this documentation. Anyway, let me know if something similar pre-exists or if such a project

Re: [yocto] [OE-core] [PATCH v4 1/3] image.bbclass: add prohibited-paths QA test

On 11/17/2017 01:21 AM, Leonardo Sandoval wrote: isn't it this class meta/classes/insane.bbclass for this type of checks? This was already discussed - the test should be on the image rather than package level: http://lists.openembedded.org/pipermail/openembedded-core/2017-November/144335.html

Re: [yocto] Trying to filter out 2 strings from EXTRA_OECONF, why doesn't this work?

On 11/17/2017 12:37 AM, Matt Schepers wrote: What do I have to do to filter out BOTH configure flags. I realize I can just write a new recipe, but I don't think that's the "correct" answer. The best way to fix this is to modify the original recipe so that all three options become PACKAGE

Re: [yocto] [OE-core] [PATCH v3 1/2] image.bbclass: add prohibited-paths QA test

On 11/15/2017 05:10 PM, Martyn Welch wrote: Sometimes we wish to ensure that files or directories are not installed somewhere that may prove detrimental to the operation of the system. For example, this may be the case if files are placed in a directory that is utilised as a mount point at run ti

Re: [yocto] [OE-core] [PATCH v2 1/2] package.bbclass: add prohibited-path qa test

On 11/14/2017 02:47 PM, Alexander Kanavin wrote: I think this situation is an image configuration problem, not a package qa problem. If a package wants to install something in a location that is deemed inappropriate by the local config, there's a reason behind it, the fix may not be ea

Re: [yocto] [OE-core] [PATCH v2 1/2] package.bbclass: add prohibited-path qa test

On 11/13/2017 09:19 PM, Martyn Welch wrote: Sometimes we wish to ensure that packages don't install files or directories somewhere that may prove detrimental to the operation of the system. For example, this may be the case if files are placed in a directory that is utilised as a mount point at r

Re: [yocto] Slightly varying builds

On 11/02/2017 06:50 PM, Colin Helliwell wrote: u-boot-w2_1.inc has the standard kind of recipe stuff. For creating env files, and files to be used for later signing, it has some _append steps, so I'm aiming to use 'DEP_IMG' to create the various files with different prefixes for the two varia

Re: [yocto] Slightly varying builds

On 11/02/2017 06:26 PM, Colin Helliwell wrote: Following on from this, I'm trying to be able to build my two versions of u-boot, in the *same* build directory. I'm not sure if this is possible, but I figured it might be: since u-boot doesn't get put into the rootfs (?), I would ideally be able

Re: [yocto] Slightly varying builds

On 11/01/2017 06:43 PM, colin.helliw...@ln-systems.com wrote: I need to build two slightly varying versions of our Yocto build – one for the production units and one for development. They differ in only a few ways – the kernel and apps are the same. But one has Dropbear, whilst the other doesn

Re: [yocto] linux-firmware: build failure

On 10/31/2017 09:04 AM, Craig McQueen wrote: Would the following be a suitable fix? -- This needs to go to oe-core list. Just one comment... # Remove python script used to check the WHENCE file - rm ${D}${nonarch_base_libdir}/firmware/check_whence.py + rm ${D}${nonarch_ba

Re: [yocto] /etc/resolv.conf symlink

On 10/30/2017 05:37 PM, Anders Montonen wrote: I'm hoping someone could clarify how the symlink generation from /etc/resolv.conf to systemd's runtime /run/systemd/resolve/resolv.conf is supposed to work when resolved is not enabled. I think we have a bug for it: https://bugzilla.yoctoproject.

Re: [yocto] [PATCH] poky: LICENSE in packagegroup makes no sense - removed

On 10/30/2017 03:51 PM, Robert Berger wrote: a/meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bb b/meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bb This patch should go to oe-core mailing list. Alex -- ___ yocto mai

<    1   2   3   4   >