Re: [yocto] [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer Days

On 2019-05-07 20:18, Behan Webster wrote: (...) > Yes, both for LF and YP it are off-the-shelf trainings that do not require much preparation. Speaking as a course maintainer for LF, keeping the YP course updated is actually a tremendous amount of work (I'm the co-maintainer for the LF YP

[yocto] Multiple MACHINEs and DISTROs: When to use own build dir, SSTATE_DIR, DL_DIR ?

Hello, we have multiple MACHINEs and DISTROs and Im wondering for which combinations I have to setup a dedicated build dir, SSTATE_DIR and DL_DIR. Information in the form of: Each (change of) MACHINE needs its dedicated SSTATE_DIR and build dir but can share DL_DIR. would be very helpful for

Re: [yocto] Multiple MACHINEs and DISTROs: When to use own build dir, SSTATE_DIR, DL_DIR ?

On Thu, 9 May 2019 at 10:47, Fabian Knapp wrote: > we have multiple MACHINEs and DISTROs and Im wondering for which > combinations I have to setup a dedicated build dir, SSTATE_DIR and DL_DIR. > > Information in the form of: > > Each (change of) MACHINE needs its dedicated SSTATE_DIR and build di

Re: [yocto] Multiple MACHINEs and DISTROs: When to use own build dir, SSTATE_DIR, DL_DIR ?

SSTATE_DIR and DL_DIR can (and should) be shared between all builds. Each MACHINE/DISTRO combination works best with it's own build_dir. Alex On Thu, 9 May 2019 at 11:47, Fabian Knapp wrote: > > Hello, > > we have multiple MACHINEs and DISTROs and Im wondering for which > combinations I have t

[yocto] [PATCH] meta-yocto-bsp: Bump to the latest stable kernel for all the BSP

Boot test for all these boards. Signed-off-by: Kevin Hao --- .../recipes-kernel/linux/linux-yocto_4.19.bbappend | 20 ++-- .../recipes-kernel/linux/linux-yocto_5.0.bbappend| 20 ++-- 2 files changed, 20 insertions(+), 20 deletions(-) diff --git a/meta-yocto

Re: [yocto] [PATCH] meta-yocto-bsp: Bump to the latest stable kernel for all the BSP

On Thu, May 9, 2019 at 8:10 AM Kevin Hao wrote: > Boot test for all these boards. > > I do have more -stable updates coming, and you are seeing some queued 5.0.x changes that I haven't sent yet (since I'm hung up on resolving a 4.19 conflict for one of the SoC branches), but yes, the changes here

[yocto] [meta-anaconda][PATCH 2/2] anaconda_support_image: Add package-management to IMAGE_FEATURES

Currently, if a target image does not contain the rpm database, any rpm queries that anaconda executes will fail. To fix this, add the rpm database to all images. Signed-off-by: Ovidiu Panait --- classes/anaconda_support_image.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[yocto] [meta-anaconda][PATCH 1/2] python3-anaconda: Fix xserver detection

When installing an image that has graphical interface, /etc/systemd/system/default.target will point to multi-user.target instead of graphical.target. To fix this, use the right rpm query to detect the presence of xserver. Signed-off-by: Ovidiu Panait --- ...aconda-payload-Fix-xserver-detection

Re: [yocto] [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer Days

On 5/9/19 12:55 AM, Bas Mevissen wrote: > On 2019-05-07 20:18, Behan Webster wrote: > > (...) > >> > Yes, both for LF and YP it are off-the-shelf trainings that do not >> require much preparation. > >> Speaking as a course maintainer for LF, keeping the YP course updated >> is actually a tremendo

Re: [yocto] [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer Days

Chiming in here On 5/7/19 11:18 AM, Behan Webster wrote: On May 7, 2019, at 2:47 AM, Bas Mevissen > wrote: On 2019-05-07 07:20, Behan Webster wrote: > On May 6, 2019, at 8:36 AM, Bas Mevissen > wrote: > On 5/6/19 12:45 PM, Josef Holzmayr wr

Re: [yocto] [PATCH] meta-yocto-bsp: Bump to the latest stable kernel for all the BSP

>From yesterday... Latest stable release of: https://github.com/jumpnow/meta-bbb My GitHub for BBB (BeagleBone Black): https://github.com/ZoranStojsavljevic/bbb-yocto Both worked out for my bash script (adopted for my needs -> sticks and ropes) and KAS tool! https://github.com/ZoranStojsavljevic/

Re: [yocto] [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer Days

> On May 9, 2019, at 8:38 AM, Rudolf J Streif wrote: > > Chiming in here > > On 5/7/19 11:18 AM, Behan Webster wrote: >>> On May 7, 2019, at 2:47 AM, Bas Mevissen >> > wrote: >>> >>> On 2019-05-07 07:20, Behan Webster wrote: >>> > On May 6, 2019, at 8:36 AM, B

Re: [yocto] [PATCH] meta-yocto-bsp: Bump to the latest stable kernel for all the BSP

On Thu, May 9, 2019 at 12:30 PM Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > From yesterday... Latest stable release of: > https://github.com/jumpnow/meta-bbb > > My GitHub for BBB (BeagleBone Black): > https://github.com/ZoranStojsavljevic/bbb-yocto > > Both worked out for my bas

Re: [yocto] [PATCH] meta-yocto-bsp: Bump to the latest stable kernel for all the BSP

There is always around, lurking, the replacement crew... Please, do not forget about that! And the replacement crew is always ahead... ;-) Zoran ___ On Thu, May 9, 2019 at 9:32 PM Bruce Ashfield wrote: > > > > On Thu, May 9, 2019 at 12:30 PM Zoran Stojsavljevic > wrote: >> >> From yesterd

[yocto] python-numpy RDEPENDS not honored?

python-numpy is being installed on my image as a dependency of one of my packages. However, none of python-numpy's RDEPENDS are currently being included on the image. When I run bitbake -e python-numpy > numpy.txt, I see that for some reason, the RDEPENDS is being overridden to a nearly empty val

Re: [yocto] python-numpy RDEPENDS not honored?

I think the problem is in the python-numpy_1.14.5.bb recipe. It does: RDEPENDS_${PN}_class-target_append = ... where it seems to need to be: RDEPENDS_${PN}_append_class-target = ... Note the position of the word append. If someone wanted to point me in the right direction, I could try to make a

[yocto] How do IMAGE_FEATURES+="tools-sdk" and TOOLCHAIN_TARGET_TASK interact?

Looking through the recipes and classes, it seems that adding "tools-sdk" to the IMAGE_FEATURES of an image just adds a relatively arbitrary list of "sdk-ish" packages to the image from packagegroup-core-sdk I had assumed that tools-sdk would duplicate the logic of "populate_sdk" somehow, so that

[yocto] [meta-security][PATCH 1/2] oe-selftest: add running cve checker

Signed-off-by: Armin Kuster --- lib/oeqa/selftest/cases/cvechecker.py | 27 +++ 1 file changed, 27 insertions(+) create mode 100644 lib/oeqa/selftest/cases/cvechecker.py diff --git a/lib/oeqa/selftest/cases/cvechecker.py b/lib/oeqa/selftest/cases/cvechecker.py new file

[yocto] [meta-security][PATCH 2/2] smack: kernel fragment update

Signed-off-by: Armin Kuster --- recipes-kernel/linux/linux-yocto-5.0/smack.cfg | 11 +-- 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/recipes-kernel/linux/linux-yocto-5.0/smack.cfg b/recipes-kernel/linux/linux-yocto-5.0/smack.cfg index 62f465a..0d5fc64 100644 --- a/recip

[yocto] Join Us – May 13th, 2019 – Live Coding with Yocto Project

Hello Everybody, The next live coding session is approaching quickly. When: May 13th, 2019, 5:00 PM CET Where: Yocto Project Twitch channel - https://www.twitch.tv/yocto_project What: Yocto Project developer, Josef Holzmayr, will show you how to create a simple layer, derive a customized image a

[yocto] Yocto image systemd debugging

Hi, How did you debug systemd running Yocto image on embedded system when services or cron jobs failed to run? Thank you. - jh -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto image systemd debugging

Figured out crond log journalctl -u crond. Which systemd daemon for auto service launch during boot? Thank you. - jh On 5/10/19, JH wrote: > Hi, > > How did you debug systemd running Yocto image on embedded system when > services or cron jobs failed to run? > > Thank you. > > - jh > -- _

[yocto] Yocto image systemd debugging

On Friday, May 10, 2019 8:00 AM JH wrote: > How did you debug systemd running Yocto image on embedded system > when services or cron jobs failed to run? What do you mean by debug? In most cases 'systemctl status ', 'systemctl --failed', system-analyze and journalctl are efficient. Sometimes I s