Re: [yocto] Yoctoproject.org cgit tags CSS

I've copied the style into the new class name. Please let me know if this looks correct to you. On Mon, Nov 9, 2020 at 12:29 PM Anders Montonen wrote: > Hi, > > Since some time, the tags in the log view of yoctoproject.org’s cgit have > not been highlighted correctly. The problem seems to be

Re: [linux-yocto] [linux-yocto-dev standard/base][PATCH 1/1] time/sched_clock: Mark sched_clock_read_begin/retry() as notrace

In message: [linux-yocto-dev standard/base][PATCH 1/1] time/sched_clock: Mark sched_clock_read_begin/retry() as notrace on 06/11/2020 quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > Since sched_clock_read_begin() and sched_clock_read_retry() are called > by notrace function

Re: [linux-yocto][yocto-kernel-cache][master/yocto-5.4][PATCH 1/2] features/igc: Add igc driver for Intel I225-LM/I225-V family

merged. Bruce In message: [linux-yocto][yocto-kernel-cache][master/yocto-5.4][PATCH 1/2] features/igc: Add igc driver for Intel I225-LM/I225-V family on 05/11/2020 Yongxin Liu wrote: > Signed-off-by: Yongxin Liu > --- > features/igc/igc.cfg | 2 ++ > features/igc/igc.scc | 5 + > 2 files

Re: [linux-yocto][linux-yocto-dev cn96xx] update for marvell-cn96xx linux-yocto-dev v5.9

In message: [linux-yocto][linux-yocto-dev cn96xx] update for marvell-cn96xx linux-yocto-dev v5.9 on 04/11/2020 Ruiqiang Hao wrote: > Hi Bruce, > > Please help to merge follow kernel code into our marvell-cn96xx repo. > > repo: > linux-yocto-dev > branch: >

[yocto] [meta-selinux][PATCH] setools: fix build with Python 3.9

The Py_UNICODE_COPY, Py_UNICODE_FILL, PyUnicode_WSTR_LENGTH, PyUnicode_FromUnicode(), PyUnicode_AsUnicode(), _PyUnicode_AsUnicode, and PyUnicode_AsUnicodeAndSize() are marked as deprecated in Python 3.9. (See: https://docs.python.org/3/whatsnew/3.9.html). But the current python3-cython (0.29.21)

[yocto] M+ & H bugs with Milestone Movements WW45

All, YP M+ or high bugs which moved to a new milestone in WW45 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 6437 Document how to set up the Yocto Project for production work

[yocto] Enhancements/Bugs closed WW45!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count r...@burtonini.com 2 akuster...@gmail.com 1 randy.macl...@windriver.com 1 david.re...@windriver.com 1 Grand Total 5 Thanks, Stephen K. Jolley Yocto Project Program Manager *

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

All, Below is the list as of top 50 bug owners as of the end of WW45 of who have open medium or higher bugs and enhancements against YP 3.3. There are 121 possible work days left until the final release candidates for YP 3.3 needs to be released. Who Count

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

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:

[yocto] cipd ensure -log-level error -root

Hi, I am getting the below error messages when trying to build meta-flutter. - Error: Command 'cipd ensure -log-level error -root -ensure-file /tmp/tmpHyUQvg.ensure' returned non-zero exit status 2 - wget: --user-agent: Invalid value ‘depot_tools/HEAD\n???’. - CalledProcessError: Command 'git

[yocto] #devtool #toolchain #yocto #warning

Hi, I am trying to use meta-flutter to my Renesas R-Car build environment. I get the below error, can anyone help me. I am not sure if it is network issue or I need to do add/remove additional configurations. * Error: Command 'cipd ensure -log-level error -root /home

[yocto] Yoctoproject.org cgit tags CSS

Hi, Since some time, the tags in the log view of yoctoproject.org’s cgit have not been highlighted correctly. The problem seems to be that in the HTML, tags are given the class “tag-annotated-deco”, which doesn’t exist in the CSS. The CSS does have a “tag-deco” style which is probably what’s

Re: [yocto] [PATCH 1/1] openssl: Add c_rehash to misc package and add perl runtime dependency - resend...

Resend to get Stephen's correct email address. On 2020-10-19 11:29 p.m., Federico Pellegrin wrote: Sorry, new to the process, adding the pull URL here: https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=fedepell/bug14083 Cheers, F. Hi Federico, Sorry for the delay. We've been

Re: [yocto] [PATCH 1/1] openssl: Add c_rehash to misc package and add perl runtime dependency

On 2020-10-19 11:29 p.m., Federico Pellegrin wrote: Sorry, new to the process, adding the pull URL here: https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=fedepell/bug14083 Cheers, F. Hi Federico, Sorry for the delay. We've been getting the 3.2 release out the door and

Re: [yocto] [gtk+3][zeus] building only with wayland backend, no x11

Do you actually need gtk+3 in your image? There is a poky configuration that builds core-image-weston without x11, and core-image-weston does pull in gtk+3, and all that happens without errors: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder-helper/tree/config.json?h=zeus#n638 so I'd

Re: [yocto] Why python3 is build native in yocto ??? #python

Understood but this is where it gets tricky for me . I am trying to compile llvmlite which depends on llvm . The problem is that because native python is used it will give me OS Error when I link LLVM build for ARM The reason I get this error is because llvmlite is looking for LLVM built for

[yocto] [gtk+3][zeus] building only with wayland backend, no x11

Hi, I am building an image based on core-image-weston. I would like to use only wayland backend, thus I defined in my machine's configuration: DISTRO_FEATURES_append = " wayland" DISTRO_FEATURES_remove = " x11" I have a problem with build of gtk+3: | checking for pango pangocairo

Re: [yocto] Why python3 is build native in yocto ??? #python

On Mon, 2020-11-09 at 09:14 +, Ross Burton wrote: > DEPEND on python3 and python3-native then. Note that whilst the python headers and library will be in recipe- sysroot, the python3 binaries will not. This is because they're designed to run on the target, not the host you're building on so

Re: [yocto] Dependencies error while compiling .

Hi Paul, I didnt get u exactly . so for these what i can do can u please suggest . On Mon, Nov 9, 2020 at 3:25 PM Paul Barker wrote: > On Mon, 9 Nov 2020 at 09:16, NIKHIL PATIL wrote: > > > > Hi, > > when i am compiling package using > > -> bitbake ostree-initrd > > We're

Re: [yocto] Dependencies error while compiling .

On Mon, 9 Nov 2020 at 09:16, NIKHIL PATIL wrote: > > Hi, > when i am compiling package using > -> bitbake ostree-initrd We're missing important output here which would show the layers, versions and key config values. > > ERROR: ostree-initrd-3-r0 do_install: Function failed:

Re: [yocto] Dependencies error while compiling .

Hi, when i am compiling package using -> bitbake ostree-initrd ERROR: ostree-initrd-3-r0 do_install: Function failed: do_install (log file is located at /data/nikhil/inti_dmsv/yocto_build/build/tmp/work/all-poky-linux/ostree-initrd/3-r0/temp/log.do_install.7163) ERROR: Logfile

Re: [yocto] Why python3 is build native in yocto ??? #python

DEPEND on python3 and python3-native then. Ross On Fri, 6 Nov 2020 at 09:34, wrote: > > I am sorry , I will explain in detail. > > so what I required is that my python3 binary should be present in both > recipe-sysroot and recipe-sysroot-native both as I need to build some python > packages

Re: [yocto] Dependencies error while compiling .

On Mon, 9 Nov 2020 at 05:12, NIKHIL PATIL wrote: > > Hi team , > while compiling a package i am getting following error :- > > Log data follows: > | DEBUG: Executing python function extend_recipe_sysroot > | NOTE: Direct dependencies are >

[yocto] [yocto-autobuilder2][RFC PATCH] config.py: add "only-x11" target to builds

This target builds and tests core-image-sato and associated SDKs, as otherwise the AB targets have been moved to core-image-weston. Signed-off-by: Alexander Kanavin --- config.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config.py b/config.py index 035a2f8..36176f8

[yocto] [RFC PATCH 3/5] config.json: replace core-image-sato with core-image-weston

I believe the time has come for YP to be defaulting to Wayland and not X11. X11 is effectively deprecated technology at this point with only minimal maintenance; standalone X server will not be developed any further, and all attention currently is towards making X apps work well under Wayland.

[yocto] [RFC PATCH 1/5] config.json: drop core-image-sato-dev from builds

core-image-sato-sdk is a superset, and a much more useful one. Signed-off-by: Alexander Kanavin --- config.json | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/config.json b/config.json index 11a2664..6d50a36 100644 --- a/config.json +++ b/config.json

[yocto] [RFC PATCH 4/5] config.json: pam is required when weston starts under systemd

Signed-off-by: Alexander Kanavin --- config.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/config.json b/config.json index def8d5a..51a540c 100644 --- a/config.json +++ b/config.json @@ -861,7 +861,7 @@ "BBTARGETS" : "core-image-weston",

[yocto] [RFC PATCH 2/5] config.json: transition ptests to weston-based images

Signed-off-by: Alexander Kanavin --- config.json | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/config.json b/config.json index 6d50a36..3e60d15 100644 --- a/config.json +++ b/config.json @@ -87,16 +87,16 @@ }, "ptest-qemu" : {

[yocto] [RFC PATCH 5/5] config.json: add a target to test standalone X11 image

Signed-off-by: Alexander Kanavin --- config.json | 5 + 1 file changed, 5 insertions(+) diff --git a/config.json b/config.json index 51a540c..5ad3017 100644 --- a/config.json +++ b/config.json @@ -681,6 +681,11 @@ ] }, +"only-x11" : { +"MACHINE" :