[yocto] [meta-oic][PATCH 3/5] iotivity-simple-client: Support pkg-config

Since IoTivity-1.3.0 Signed-off-by: Philippe Coval --- .../files/0002-build-Use-pkg-config.patch | 43 ++ .../iotivity-simple-client_1.1.0.bb| 8 +++- 2 files changed, 50 insertions(+), 1 deletion(-) create mode

[yocto] [meta-oic][PATCH 2/5] Add recipe for IoTivity 1.3.0

Note that SECURITY is now enabled but might cause issues on some examples. Bug: https://jira.iotivity.org/browse/IOT-2651 Signed-off-by: Philippe Coval --- README | 2 +-

[yocto] [meta-oic][PATCH 4/5] iotivity-sensorboard: Support pkg-config

Since IoTivity-1.3.0 Signed-off-by: Philippe Coval --- .../files/0003-server-Port-to-iotivity-1.2.0.patch | 68 ++ .../files/0004-build-Use-pkg-config.patch | 48 +++ .../iotivity-sensorboard_1.0.0.bb | 11

[yocto] [meta-oic][PATCH 5/5] Add recipe for IoTivity 1.3.1

Note that fail on warning flag has been added, and can be used in .bbappend if needed after reporting bugs: http://wiki.iotivity.org/report Bug: https://jira.iotivity.org/browse/IOT-2651 Signed-off-by: Philippe Coval --- README |

[yocto] [meta-oic][PATCH 1/5] iotivity_1.2.1: Hotfix: Add ORIGIN rpath for binutils-2.29

Set RPATH to ORIGIN as supported by gcc/ld (-rpath=\$ORIGIN) Observed issue on poky master was: ld: warning: libconnectivity_abstraction.so, \ needed by out/yocto/x86_64/release/liboctbstack.so, not found (try using -rpath or -rpath-link) out/yocto/x86_64/release/liboctbstack.so: \

Re: [yocto] add kernel modules & dtbo's for Raspberry Pi3

On Wed 2017-12-20 @ 11:40:50 PM, Greg Wilson-Lindberg wrote: > I'm building an image for the Raspberry Pi 3 and I'm trying to add some > modules to the kernel and I need to add some device tree overlays. The > modules and overlays are part of the kernel, just not built by default. > > For the

Re: [yocto] [meta-raspberrypi] linux kernel rt

hi Andreas, so i need to integrate it now into my meta layer. Because i am using the meta-raspberry pi. To put it into my local meta-layer: should i copy the recipies-kernel->linux-raspberrypi4.9 only is there some other files i need to copy? I will be working with audio/wlan/bluetooth, no need

[yocto] how to deal with the dependency explosion caused by enabling x11vnc

Hello, I'd like to put a vnc server on my target. My embedded target has an onboard display and runs an application that drives the display directly via the framebuffer. ( no xorg onboard ) I would like to use x11vnc ( with the --rawfb option ) however I'm having a hard time justifying the

Re: [yocto] add kernel modules & dtbo's for Raspberry Pi3

Hi Trevor, Other than the fact that I was using '()' instead of '{}' for the file name, your catch of the missing ':' got the file include fixed. And your suggestion for including the Device Tree Overlays was perfect. Thanks, I seem to have something still messed up in the kernel configs

Re: [yocto] Some trivial question about git update-ref refs/heads/rocko ...

Hello Andre, > To switch from rocko to master, try: > > git fetch origin > git checkout -B master origin/master This did the trick... Thank you! I always thought that I actually initially fetched master release, but it appears that I fetched rocko as genesis release. The conclusion/fact

Re: [yocto] QA cycle report for 2.3.3 RC1

On Wed, 2017-12-20 at 20:25 -0800, Cruz, Libertad wrote: > Hello All, > Enjoy viewing the full Report for 2.3.3 RC1:  https://wiki.yoctoproje > ct.org/wiki/WW51_-_2017-12-20-_Full_Test_Cycle_-_2.3.3_rc1 > > === Summary > > The QA cycle for release 2.3.3 RC1 is complete.  There are 4

Re: [yocto] [meta-raspberrypi] linux kernel rt

On Thu, Dec 21, 2017 at 5:08 PM, Andrei Gherzan wrote: > Hi all, > > On Thu, Dec 14, 2017 at 12:09 PM, Andreas Müller > wrote: > >> On Thu, Dec 14, 2017 at 11:40 AM, Mirza Krak >> wrote: >> >>> 2017-12-14 9:41 GMT+01:00 Andreas

Re: [yocto] [meta-raspberrypi] linux kernel rt

Hi all, On Thu, Dec 14, 2017 at 12:09 PM, Andreas Müller wrote: > On Thu, Dec 14, 2017 at 11:40 AM, Mirza Krak wrote: > >> 2017-12-14 9:41 GMT+01:00 Andreas Müller : >> > On Thu, Dec 14, 2017 at 2:58 AM, Sherif Omran < >>

Re: [yocto] Layer documentation for meta-raspberrypi

Nice. Good job. -- Andrei Gherzan On Mon, Dec 18, 2017 at 9:57 PM, Mirza Krak wrote: > On Dec 18, 2017 20:50, "Paul Barker" wrote: > > On Mon, Dec 11, 2017 at 12:20 PM, Paul Barker > wrote: > > On Mon, Dec 11, 2017 at 12:08

Re: [yocto] [meta-raspberrypi] How to modify KERNEL_DEVICETREE?

Hi, You need to make that variable available in both sdcard generation code which resides in the image recipe and in the kernel recipe. You can do this by modifying that variable from local.conf (distro would work too I think but it doesn't sounds like the right place to be). -- Andrei Gherzan

[yocto] How to config kernel in my own meta layer?

Greetings, I have a recipes that requires 128MB of CMA allocation for DMA. I followed the instruction in http://www.yoctoproject.org/docs/1.6/kernel-dev/kernel-dev.html#changing-the-configuration and did the following: My recipes structure: meta-mylayer\recipes-my\uio-test\ 1. Then in

[yocto] FW: QA cycle report for 2.3.3 RC1

Machine was rebooted last week 12/12 -$ who -b system boot 2017-12-12 09:18 -$ uptime -s 2017-12-12 09:19:28 -Original Message- From: Perez Carranza, Jose Sent: Thursday, December 21, 2017 8:57 AM To: Purdie, Richard ; Cruz, Libertad

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

Particularly: 1) Rebase and integrate (most of) Robert's patches 2) Add musl testing support (a notorious source of failures) 3) Rework testimage support to be more straigtforward and usable locally by maintainers 4) Other things :) The following changes since commit

[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

[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

[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 +++

[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

[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

[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 @@

[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

[yocto] Python cryptography failing due to undefined symbol: pthread_atfork

Hi there, just did a migration to Rocko and am witnessing" root@device:~# python3 Python 3.5.3 (default, Dec 20 2017, 02:02:22) [GCC 7.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from cryptography.hazmat.bindings._openssl import

[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

[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

[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 ---

[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

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

There's some logic to ascribe failures to specific recipe upgrade commits; it's prone to mismatches and is lacking context about what else was upgraded. Let's make testimage support available for local maintainer use only - unattended mass-upgrades will not try to run testimages.

[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

Re: [yocto] libgfortran or cross compiling a fortran application

Hi! Just in case, someone (else) stumbles across this: https://bugzilla.yoctoproject.org/show_bug.cgi?id=12394 http://cgit.openembedded.org/openembedded-core/commit/?id=2c2f20a9756eccafac776e45e319af7666e6da96 fixes the issue on rocko for me. Regards, Matthias On 12/20/2017 11:30 AM,

[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

[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

[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 *

[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

[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

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

This adds enormously to run time, and is not particularly necessary when running locally. If something fails, it's best to let the maintainer sort it out as soon as possible, rather than try to guess what needs to be excluded. Also, do not build a separate ptest image; ptests will be added to the

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

Particularly: 1) determine per-package if ptest is supported, and add to the list of packages to install accordingly 2) remove broken code that finds image logs in the build directory; this will be replaced in the following commit 3) remove code that parses said logs for specific package failures;

[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 @@