date:20220404

Re: [yocto] [meta-zephyr][PATCH] zephyr-kernel-src: add whitespace to fix File not found during build

2022-04-04 Thread Naveen Saini



> -Original Message-
> From: yocto@lists.yoctoproject.org  On
> Behalf Of Davide Gardenal
> Sent: Monday, April 4, 2022 9:17 PM
> To: yocto@lists.yoctoproject.org
> Cc: Davide Gardenal 
> Subject: [yocto] [meta-zephyr][PATCH] zephyr-kernel-src: add whitespace to
> fix File not found during build
> 
> Signed-off-by: Davide Gardenal 
> ---
>  .../recipes-kernel/zephyr-kernel/zephyr-kernel-src-3.0.0.inc| 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-
> src-3.0.0.inc b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-
> kernel-src-3.0.0.inc
> index f4ea7d3..61a5076 100644
> --- a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-
> 3.0.0.inc
> +++ b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-
> 3.0.0.inc
> @@ -69,4 +69,4 @@ SRCREV_zscilib =
> "12bfe3f0a9fcbfe3edab7eabc9678b6c62875d34"
>  ZEPHYR_BRANCH = "v3.0-branch"
>  PV = "3.0.0+git${SRCPV}"
> 
> -SRC_URI += "file://0001-lvgl-add-support-for-lvgl-v8.2.0.patch"
> +SRC_URI += "file://0001-lvgl-add-support-for-lvgl-v8.2.0.patch "

[Naveen] It does not apply. Did you send any patch previously, which I missed ?

https://git.yoctoproject.org/meta-zephyr/tree/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-3.0.0.inc#n70

> --
> 2.32.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56664): https://lists.yoctoproject.org/g/yocto/message/56664
Mute This Topic: https://lists.yoctoproject.org/mt/90241245/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Enhancements/Bugs closed WW14!

2022-04-04 Thread Stephen Jolley

All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


randy.macl...@windriver.com

7


r...@burtonini.com

2


richard.pur...@linuxfoundation.org

1


Grand Total

10

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56663): https://lists.yoctoproject.org/g/yocto/message/56663
Mute This Topic: https://lists.yoctoproject.org/mt/90256533/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Current high bug count owners for Yocto Project 3.5

2022-04-04 Thread Stephen Jolley

All,

Below is the list as of top 39 bug owners as of the end of WW14 of who have
open medium or higher bugs and enhancements against YP 3.5.   There are 18
possible work days left until the final release candidates for YP 3.5 needs
to be released.


Who

Count


michael.opdenac...@bootlin.com

34


r...@burtonini.com

25


randy.macl...@windriver.com

15


bruce.ashfi...@gmail.com

13


tim.orl...@konsulko.com

12


david.re...@windriver.com

11


richard.pur...@linuxfoundation.org

11


trevor.gamb...@windriver.com

7


mhalst...@linuxfoundation.org

7


bluelightn...@bluelightning.org

6


sakib.sa...@windriver.com

6


chee.yang@intel.com

4


hongxu@windriver.com

3


jpewhac...@gmail.com

3


kai.k...@windriver.com

2


qi.c...@windriver.com

2


pgowda@gmail.com

2


saul.w...@windriver.com

2


ms...@mvista.com

2


akuster...@gmail.com

2


jon.ma...@arm.com

1


mostthings...@gmail.com

1


alexandre.bell...@bootlin.com

1


yi.z...@windriver.com

1


sundeep.kokko...@gmail.com

1


pokyli...@reliableembeddedsystems.com

1


pa...@zhukoff.net

1


raj.k...@gmail.com

1


and...@gherzan.com

1


aeh...@gmail.com

1


thomas.per...@bootlin.com

1


matthew...@posteo.net

1


ticot...@gmail.com

1


nicolas.deche...@linaro.org

1


jas...@gmail.com

1


mark.ha...@kernel.crashing.org

1


open.sou...@oleksandr-kravchuk.com

1


john.kaldas.e...@gmail.com

1


alejan...@enedino.org

1


Grand Total

188

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56662): https://lists.yoctoproject.org/g/yocto/message/56662
Mute This Topic: https://lists.yoctoproject.org/mt/90256473/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2022-04-04 Thread Stephen Jolley

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 394
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now,  "3.5, "3.6", "3.99" and "Future", the more pressing/urgent
issues being in "3.5" and then "3.6".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56661): https://lists.yoctoproject.org/g/yocto/message/56661
Mute This Topic: https://lists.yoctoproject.org/mt/90256454/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Logical Volumes not present at boot time with sysvinit, mountall.sh #honister

2022-04-04 Thread bgctkd

I am seeing that logical volumes in /etc/fstab are not present at boot time 
when mountall.sh is being run
on my image based off Poky/Honister, with lvm2 recipe

After boot, once I log in, lsblk shows the mount points and "mount -a" works as 
expected.  At boot, alas no dice.

Any suggestions on how to get the logical volumes in place so that they can be 
mounted from /etc/fstab during boot when mountall.sh is being run?

*During boot:*
At Beginning of mountall.sh
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 55.9G 0 disk
|-sda1 8:1 0 101.9M 0 part
`-sda2 8:2 0 55.8G 0 part
Mon Apr 4 17:33:05 UTC 2022
After mounting file systems

*Post Boot:*
root@intel-corei7-64:/tmp# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 55.9G 0 disk
|-sda1 8:1 0 101.9M 0 part
`-sda2 8:2 0 55.8G 0 part
|-mount-pt-a 252:0 0 1000M 0 lvm
|-mount-pt-b 252:1 0 100M 0 lvm
|-mount-pt-c 252:2 0 6.3G 0 lvm

Thanks,

Bruce

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56660): https://lists.yoctoproject.org/g/yocto/message/56660
Mute This Topic: https://lists.yoctoproject.org/mt/90249886/21656
Mute #honister:https://lists.yoctoproject.org/g/yocto/mutehashtag/honister
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-zephyr][PATCH] zephyr-kernel-src: add whitespace to fix File not found during build

2022-04-04 Thread Davide Gardenal

Signed-off-by: Davide Gardenal 
---
 .../recipes-kernel/zephyr-kernel/zephyr-kernel-src-3.0.0.inc| 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-3.0.0.inc 
b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-3.0.0.inc
index f4ea7d3..61a5076 100644
--- a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-3.0.0.inc
+++ b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-3.0.0.inc
@@ -69,4 +69,4 @@ SRCREV_zscilib = "12bfe3f0a9fcbfe3edab7eabc9678b6c62875d34"
 ZEPHYR_BRANCH = "v3.0-branch"
 PV = "3.0.0+git${SRCPV}"
 
-SRC_URI += "file://0001-lvgl-add-support-for-lvgl-v8.2.0.patch"
+SRC_URI += "file://0001-lvgl-add-support-for-lvgl-v8.2.0.patch "
-- 
2.32.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56659): https://lists.yoctoproject.org/g/yocto/message/56659
Mute This Topic: https://lists.yoctoproject.org/mt/90241245/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-security][PATCH] fscrypt: update dependecy from go-dep-native to go-native

2022-04-04 Thread Davide Gardenal

Signed-off-by: Davide Gardenal 
---
 recipes-security/fscrypt/fscrypt_1.0.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-security/fscrypt/fscrypt_1.0.0.bb 
b/recipes-security/fscrypt/fscrypt_1.0.0.bb
index 66bf429..663d8e2 100644
--- a/recipes-security/fscrypt/fscrypt_1.0.0.bb
+++ b/recipes-security/fscrypt/fscrypt_1.0.0.bb
@@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = 
"file://src/${GO_IMPORT}/LICENSE;md5=3b83ef96387f14655fc854dd
 BBCLASSEXTEND = "native nativesdk"
 
 # fscrypt depends on go and libpam
-DEPENDS += "go-dep-native libpam"
+DEPENDS += "go-native libpam"
 
 SRCREV = "92b1e9a8670ccd3916a7d24a06cab1e4c9815bc4"
 SRC_URI = "git://github.com/google/fscrypt.git;branch=master;protocol=https"
-- 
2.32.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56658): https://lists.yoctoproject.org/g/yocto/message/56658
Mute This Topic: https://lists.yoctoproject.org/mt/90240814/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-security][PATCH] clamav: add COMPATIBLE_HOST to fix build error

2022-04-04 Thread Davide Gardenal

Add COMPATIBLE_HOST to match what is found in glibc
to avoid build error when using musl

Signed-off-by: Davide Gardenal 
---
 recipes-scanners/clamav/clamav_0.104.0.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/recipes-scanners/clamav/clamav_0.104.0.bb 
b/recipes-scanners/clamav/clamav_0.104.0.bb
index f0889de..ae2d292 100644
--- a/recipes-scanners/clamav/clamav_0.104.0.bb
+++ b/recipes-scanners/clamav/clamav_0.104.0.bb
@@ -6,6 +6,8 @@ LICENSE = "LGPL-2.1"
 
 DEPENDS = "glibc llvm libtool db openssl zlib curl libxml2 bison pcre2 json-c 
libcheck"
  
+COMPATIBLE_HOST:libc-musl:class-target = "null"
+
 LIC_FILES_CHKSUM = 
"file://COPYING.txt;beginline=2;endline=3;md5=f7029fbbc5898b273d5902896f7bbe17"
 
 # July 27th
-- 
2.32.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56657): https://lists.yoctoproject.org/g/yocto/message/56657
Mute This Topic: https://lists.yoctoproject.org/mt/90240805/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Specified SDKMACHINE value is not valid

2022-04-04 Thread Ross Burton

Is Raspian 32- or 64-bit?  We don't suppose 32-bit arm SDKs.

As Khem said, set SDKMACHINE to i686 explicitly to avoid this.  Note
that compiling on a RPi4 is *very slow*.

Ross

On Sat, 2 Apr 2022 at 17:37, jchludzinski via lists.yoctoproject.org
 wrote:
>
> I’m actually trying this on an RP4 running Raspbian.
>
> On 2022-04-02 12:15, Khem Raj wrote:
> > On Sat, Apr 2, 2022 at 1:47 AM jchludzinski 
> > wrote:
> >>
> >> $ git clone git://git.yoctoproject.org/poky.git
> >> $ cd ./poky
> >> $ git checkout yocto-3.4.2
> >> $ cd ..
> >> $ source ./poky/oe-init-build-env
> >> $ cd ./build
> >> $ time bitbake core-image-minimal
> >> ...
> >> ERROR:  OE-core's config sanity checker detected a potential
> >> misconfiguration.
> >> Either fix the cause of this error or at your own risk disable the
> >> checker (see sanity.conf).
> >> Following is the list of potential problems / advisories:
> >>
> >> Specified SDKMACHINE value is not valid
> >>
> >>
> >> Summary: There was 1 WARNING message shown.
> >> Summary: There was 1 ERROR message shown, returning a non-zero exit
> >> code.
> >>
> >> 
> >> Executed in3.92 secsfish   external
> >>usr time1.07 secs9.77 millis1.06 secs
> >>sys time0.18 secs2.96 millis0.17 secs
> >>
> >>
> >>
> >> On 2022-04-01 18:09, Khem Raj wrote:
> >>
> >> On Fri, Apr 1, 2022 at 2:02 PM jchludzinski 
> >> wrote:
> >>
> >>
> >> But obviously commented out.
> >>
> >> On 2022-04-01 16:43, jchludzinski via lists.yoctoproject.org wrote:
> >>
> >> There's this:
> >> #SDKMACHINE ?= "i686"
> >>
> >>
> >> OK it should be ok then. Can you describe your steps to setup the
> >> system?
> >> maybe there is some caveat
> >>
> >>
> >> ---John
> >>
> >> On 2022-04-01 16:22, Khem Raj wrote:
> >>
> >> On Fri, Apr 1, 2022 at 1:09 PM jchludzinski via
> >> lists.yoctoproject.org
> >> [1 [1]]  wrote:
> >>
> >> I'm trying an experiment building yocto/OE on a Raspberry Pi 4 to
> >> host on the same RP4. Admittedly, a not practical platform for
> >> this
> >> purpose but it should work.
> >>
> >> I'm trying to target the ARM ISA for the image using yocto-3.4.2.
> >> I've tried simply using the default setting and end up with:
> >>
> >> _ERROR:  OE-core's config sanity checker detected a potential
> >> misconfiguration._
> >> _Either fix the cause of this error or at your own risk
> >> disable
> >> the checker (see sanity.conf)._
> >> _Following is the list of potential problems / advisories:_
> >> _ _
> >> _Specified SDKMACHINE value is not valid_
> >>
> >> I've tried editing ./conf/local.conf:
> >>
> >> MACHINE ?= "qemuarm64"
> >>
> >> #MACHINE ??= "qemux86-64"
> >>
> >>
> >> It's complaining about SDKMACHINE setting which is a separate
> >> variable, can you check your local.conf if it's set to something
> >>
> >> But this accomplishes nothing. Needless to say, I'm a yacto/OE
> >> newbie, so any suggestions would be greatly appreciated.
> >
> > are you on a x86_64 host? Secondly try to uncomment SDKMACHINE setting
> > in local.conf
> > and see if it helps. Also check if your default shell is bash or dash.
> >
> >>
> >> ---John
> >>
> >>
> >> Links:
> >> --
> >> [1] http://lists.yoctoproject.org
> >>
> >>
> >>
> >> Links:
> >> --
> >> [1] http://lists.yoctoproject.org
> >>
> >>
> >>
> >>
> >>
>
> --
> NULL
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56656): https://lists.yoctoproject.org/g/yocto/message/56656
Mute This Topic: https://lists.yoctoproject.org/mt/90188098/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Building a core-image-weston with custom app using rust and gtk3

2022-04-04 Thread Alexander Kanavin

It helps if you show the error messages. Otherwise, the only thing we can
say in response is 'yes, apparently'.

Alex

On Sat, 2 Apr 2022 at 10:53, Artur Czajkowski  wrote:

> Hello,
> I'm having real difficulties in compiling a Rust app that uses gtk3 (this
> app successfully builds and runs on my host machine). I'm on the master
> branch of poky, using rust 1.59.
> Is this still untested and unstabilized feature, that is gtk-rs bindings
> in yocto?
>
> Thank you
>
> --
>
>
> Best regards
> *Artur Czajkowski*
>
> https://marketplace.visualstudio.com/items?itemName=GitAtomic.GitAtomic
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56655): https://lists.yoctoproject.org/g/yocto/message/56655
Mute This Topic: https://lists.yoctoproject.org/mt/90197556/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-zephyr][PATCH] zephyr-kernel-src: add whitespace to fix File not found during build

[yocto] Enhancements/Bugs closed WW14!

[yocto] Current high bug count owners for Yocto Project 3.5

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[yocto] Logical Volumes not present at boot time with sysvinit, mountall.sh #honister

[yocto] [meta-zephyr][PATCH] zephyr-kernel-src: add whitespace to fix File not found during build

[yocto] [meta-security][PATCH] fscrypt: update dependecy from go-dep-native to go-native

[yocto] [meta-security][PATCH] clamav: add COMPATIBLE_HOST to fix build error

Re: [yocto] Specified SDKMACHINE value is not valid

Re: [yocto] Building a core-image-weston with custom app using rust and gtk3

10 matches

Site Navigation

Mail list logo

Footer information