Re: [yocto] [OE-core] Yocto Project Status WW07'20

Planned upcoming dot releases: * YP 2.7.3 built and in QA I didn't see any notification for this build. Am I missing something? Thanks, Sangeeta From: openembedded-core-boun...@lists.openembedded.org On Behalf Of sjolley.yp...@gmail.com Sent: Wednesday, 19 February, 2020 12:10 AM To:

Re: [yocto] QA Cycle report for build (yocto-3.0.2.rc2)

> -Original Message- > From: Mittal, Anuj > Sent: Thursday, 20 February, 2020 11:35 AM > To: Richard Purdie ; akuster808 > ; Jain, Sangeeta ; > yocto@lists.yoctoproject.org > Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv > ; Yeoh, Ee Peng ; Chan, > Aaron Chun Yew ;

Re: [yocto] Modified GENIVI Cannelloni recipe with strange side effects

Hello Laurent, U R correct (and why I am not surprised?!). :-) The correct recipe is here (it becomes very simplistic, seems): https://github.com/ZoranStojsavljevic/meta-socketcan/blob/master/recipes-can/cannelloni/cannelloni.bb I have (out of my ignorance) one question, which confuses me: Why

Re: [yocto] QA Cycle report for build (yocto-3.0.2.rc2)

> On Wed, 2020-02-19 at 14:41 -0800, akuster808 wrote: > > > > On 2/18/20 11:33 PM, Jain, Sangeeta wrote: > > > Hi All, > > > > > > This is the full report for yocto-3.0.2.rc2: > > > https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib > > > /tree/?h=intel-yocto-testresults > > > >

Re: [yocto] You advice to append environment set up to local root shell profile

May be I should append to shells script. On 2/20/20, JH wrote: > Hi, > > I want to setup export LD_LIBRARY_PATH and export PATH to the > /home/root shell profile, the oe-core base-files has a profile file, > is it a right way to copy that file to my application layer, to extend > it and to add

[yocto] You advice to append environment set up to local root shell profile

Hi, I want to setup export LD_LIBRARY_PATH and export PATH to the /home/root shell profile, the oe-core base-files has a profile file, is it a right way to copy that file to my application layer, to extend it and to add new path to export LD_LIBRARY_PATH and export PATH? I'll handle it by a

Re: [yocto] QA Cycle report for build (yocto-3.0.2.rc2)

On 2/19/20 2:42 PM, Richard Purdie wrote: On Wed, 2020-02-19 at 14:41 -0800, akuster808 wrote: On 2/18/20 11:33 PM, Jain, Sangeeta wrote: Hi All, This is the full report for yocto-3.0.2.rc2:

Re: [yocto] Issue while adding the support for TLS1.3 in existing krogoth yocto #yocto #yocto #yocto #yocto #apt #raspberrypi #yocto

Hi, On Tue, Feb 18, 2020 at 01:20:25PM +0530, amaya jindal wrote: >Thanks for your prompt reply. But is not there any way similar to add >support for TLS1.3 instead of moving to new yocto releases openssl is tricky to update and requires backporting fixes for many, many recipes to get

Re: [yocto] Debugging gdb built by Yocto

On Tue, 2020-02-18 at 11:26 -0500, Patrick Doyle wrote: > Does anybody have any tips or tricks for how I might debug the > (cross-canadian) gdb built by Yocto's SDK? > > I need to add some printf's to the gdb code to help track down why > something isn't working, but none of my traditional >

Re: [yocto] Debugging gdb built by Yocto

On 2/18/20 8:26 AM, Patrick Doyle wrote: Does anybody have any tips or tricks for how I might debug the (cross-canadian) gdb built by Yocto's SDK? I need to add some printf's to the gdb code to help track down why something isn't working, but none of my traditional

Re: [yocto] do_rootfs task took long time to finish

On 2/17/20 11:55 PM, Marek Belisko wrote: Hi, I'm debugging strange issue that do_rootfs task took ~50 minutes. I enabled buildstats and from that I learned it's quite long. Any ideas how to debug this issue? My idea was to add timestamp to do_rootfs tasks but I'm not sure if it's even

[yocto] [meta-updater] [meta-updater-raspberrypi] ERROR: No recipes available for: ..../meta-updater-raspberrypi/recipes-bsp/u-boot/libubootenv_%.bbappend

I'm trying to add support for ostree to out boot2qt yocto warrior build for raspberry pi4. I've added meta-updater & meta-updater-raspberrypi to the build and when I start bitbake I get the following error: ERROR: No recipes available for:  

Re: [yocto] how to reuse generated library in a nativesdk recipe #sdk #systemd

> DEPENDS_class-target += "systemd" You surely meant DEPENDS_append_class-target = " systemd" here On Wed, Feb 19, 2020 at 10:48 PM Mikko Rapeli wrote: > Hi, > > On Wed, Feb 19, 2020 at 01:37:19AM -0800, Armando Hernandez wrote: > > Hello, > > > > I have a recipe that builds a library. The

Re: [yocto] Opentk Support

On Wed, 19 Feb 2020 at 21:45, Sheraz Ali wrote: > Does anyone know how to enable opentk in yocto ( i.e is it available ) https://layers.openembedded.org/layerindex/branch/master/recipes/?q=opentk says that there are not any known recipes, so you'll have to write one yourself. Ross

Re: [yocto] Change RO rootfs failed RF Kill Switch Status and Failed to start Run pending postinsts

It also seems mwifiex_sdio tried to write to RO rootfs and failed and triggled RF Killm, does mwifiex_sdio needs some system directories for RW? [ 26.636845] mwifiex_sdio mmc0:0001:1: mwifiex_process_cmdresp: cmd 0x242 fain Starting Load/Save RF Kill Switch Status... [ 26.852990]

[yocto] Yocto Project Status WW07'20

Current Dev Position: YP 3.1 M3 Next Deadline: YP 3.1 M3 build date 2/24/2020 Next Team Meetings: * Bug Triage meeting Thursday Feb. 20th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Mar. 3rd at 8am PDT (

[yocto] do_rootfs task took long time to finish

Hi, I'm debugging strange issue that do_rootfs task took ~50 minutes. I enabled buildstats and from that I learned it's quite long. Any ideas how to debug this issue? My idea was to add timestamp to do_rootfs tasks but I'm not sure if it's even possible. Thanks. BR, marek -- as simple and

Re: [OE-core] [yocto] Change RO rootfs failed RF Kill Switch Status and Failed to start Run pending postinsts

On Tue, Feb 18, 2020 at 08:43:01PM +1100, JH wrote: > Hi Mikko, > > On 2/18/20, mikko.rap...@bmw.de wrote: > > I think you may be missing volatile-binds package and service from your > > image. > > See poky/meta/recipes-core/volatile-binds/volatile-binds.bb > > I got the source in my build

Re: [yocto] [opkg-devel] [opkg-utils PATCH] Makefile: add opkg-feed to UTILS

LGTM, merged! On 2/17/20 5:57 PM, Alex Stewart wrote: * Add the opkg-feed script to UTILS so that it is installed with a `make install`. * Clean up the UTILS variable declaration to be a little more diffable. Signed-off-by: Alex Stewart --- Makefile | 17 ++--- 1 file

[yocto] Debugging gdb built by Yocto

Does anybody have any tips or tricks for how I might debug the (cross-canadian) gdb built by Yocto's SDK? I need to add some printf's to the gdb code to help track down why something isn't working, but none of my traditional get-ready-to-debug-this-code techniques are working. How can I run the

[yocto] oe-core recipe for defining directories in /

Hi, Which recipe defines all directories in "/"? I need to make a bbapand to add directories to /. Thank you. Kind regards, - jh -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#48486): https://lists.yoctoproject.org/g/yocto/message/48486 Mute

[yocto] Opentk Support

Hi,Does anyone know how to enable opentk in yocto ( i.e is it available )Thanks and RegardsSheraz Ali Shah-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#48489): https://lists.yoctoproject.org/g/yocto/message/48489 Mute This Topic:

Re: [yocto] [OE-core] oe-core recipe for defining directories in /

On 2/19/20 4:29 AM, Quentin Schulz wrote: > Hi JH, > > On Wed, Feb 19, 2020 at 09:12:08PM +1100, JH wrote: >> Hi, >> >> Which recipe defines all directories in "/"? I need to make a bbapand >> to add directories to /. >> > > None. Or all of them, depends on how one sees it. He is correct,

Re: [OE-core] [yocto] Change RO rootfs failed RF Kill Switch Status and Failed to start Run pending postinsts

(trimming lists to yocto only) Hi, I think you may be missing volatile-binds package and service from your image. See poky/meta/recipes-core/volatile-binds/volatile-binds.bb It may be missing /var/log but with systemd there should not be needs to write to that location after image builds...

Re: [OE-core] [yocto] Change RO rootfs failed RF Kill Switch Status and Failed to start Run pending postinsts

Hi Mikko, On 2/18/20, mikko.rap...@bmw.de wrote: > I think you may be missing volatile-binds package and service from your > image. > See poky/meta/recipes-core/volatile-binds/volatile-binds.bb I got the source in my build system, it is zeus:

[yocto] Zeus failed DHCP

Hi, My build connman on Thud works on WiFi, but Zeus does not work, the connman could not get WiFi DHCP response, it puts a local IP address 169.254.24.188 to my WiFi interface. Has anyone found that the problem in Zeus or it just me may be miss some packages or configuration? What are packages

Re: [yocto] Change RO rootfs failed RF Kill Switch Status and Failed to start Run pending postinsts

Hi Belisko, Thanks for your resonse. On 2/18/20, Belisko Marek wrote: > Can you pls provide output of systemctl status systemd-rfkill > There should be some more info what issue is. Failed at step STATE_DIRECTORY spawning /lib/systemd/systemd-rfkill: Read-only file system, did it try to write

Re: [yocto] [OE-core] Yocto Project Status WW07'20

On Tue, 18 Feb 2020 at 17:10, wrote: > >- With the git infrastructure issue updated, we now have centos8 >workers added to the autobuilder. > > What are the current plans for centos 7? Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online

Re: [yocto] [OE-core] Yocto Project Status WW07'20

On Tue, 2020-02-18 at 17:44 +0100, Alexander Kanavin wrote: > On Tue, 18 Feb 2020 at 17:10, wrote: > > With the git infrastructure issue updated, we now have centos8 > > workers added to the autobuilder. > > > > What are the current plans for centos 7? Project members are keen to see support

Re: [OE-core] [yocto] Change RO rootfs failed RF Kill Switch Status and Failed to start Run pending postinsts

Hi Mikko, On 2/18/20, mikko.rap...@bmw.de wrote: > Well I have zeus and am using read-only rootfs with volatile binds and > I did not need anything extra. I would dig into this /var/log thing > and patch it away. I use systemd journal so no need for syslogs. I actually not too worry about the

[linux-yocto][linux-yocto-dev standard/base][PATCH] tipc: fix successful connect() but timed out

From: Tuong Lien In commit 9546a0b7ce00 ("tipc: fix wrong connect() return code"), we fixed the issue with the 'connect()' that returns zero even though the connecting has failed by waiting for the connection to be 'ESTABLISHED' really. However, the approach has one drawback in conjunction with

Re: [yocto] Change RO rootfs failed RF Kill Switch Status and Failed to start Run pending postinsts

Hi, On Tue, Feb 18, 2020 at 2:00 AM JH wrote: > > Hi, > > Apologize for the cross posting. > > I am running kernel 4.19.75 on iMX6 customized device with WiFi and 4G > LTE, it was running well in an RW rootfs. After I have just changed > rootfs to RO UBIFS partition, it failed RF Kill and

Re: [yocto] Modified GENIVI Cannelloni recipe with strange side effects

Hi Zoran, I just saw your reply now. I think that you might want to remove the INHIBIT_SYSROOT_STRIP and other INHIBIT_* options from your recipe. For reference a message from Khem warning that this option should be used sparingly: *

Re: [RAUC] Private: Re: [yocto] #yocto update the kernel with a rauc bundle

Hi Hans, Am 18.02.20 um 15:06 schrieb Hans-Ulrich Schlieben: > Hi Enrico, > > I just answered your first mail on the website and thought that will > automatically reply to all. Added all lists now, hope these are correct. ah, I wasn't even aware that there is a website for this ;) > Thanks to

[yocto] [meta-mingw][PATCH] gcc/binutils: Allow plugins to be enabled on cross-canadian toolchain

As of GCC 8, plugin support is available with mingw. If the plugins are enabled in the regular binutils/gcc configurations, carry over that configuration with the mingw versions as well. When plugins are enabled, they produce a file called [plugin].dll.a. This causes the debugsrc processor to

[yocto] package QA & missing runtime dependency alerting (thud)

Hello, We occasionally see our build fail due to package QA issues, specifically: ERROR: gawk-4.2.1-r0 do_package_qa: QA Issue: /usr/lib/gawk/ptest/test/fcall_exit.awk contained in package gawk-ptest requires /bin/awk, but no providers found in RDEPENDS_gawk-ptest? [file-rdeps], I'm wondering

[yocto] how to reuse generated library in a nativesdk recipe #sdk #systemd

Hello, I have a recipe that builds a library. The recipe specifies an additional package "${PN}-systemd" along with other systemd related variables and finally it instructs that the package should be built with "-DWITH_SYSTEMD=ON" being passed to cmake. So far so good. But, I extended this

Re: [yocto] Incrementally building constantly changing application source in a workflow-friendly way with #yocto

Hi Alexander, Based on your and Oliver Westermann's help, I came up with something that works for our project requirements: My application bitbake file looks like this: EXTERNALSRC = "${@os.path.abspath(os.path.join(os.path.dirname(d.getVar('FILE')), '..', '..', 'src'))}" inherit externalsrc

[yocto] [meta-selinux][PATCH] audit: add clock_settime64 syscall

From: Mingli Yu On 32bit system, After upgrade glibc to 2.31 # strace -o /tmp/test.log date -s 09:16:45 # tail -f /tmp/test.log close(3)= 0 stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=114, ...}) = 0 clock_settime64(CLOCK_REALTIME,