Re: [yocto] [meta-security][PATCH] meta-security: Drop ${PYTHON_PN}

2024-02-22 Thread Anuj Mittal 
On Tue, 2024-02-20 at 12:32 -0500, Armin Kuster wrote:
> +    pyhton3-ctypes \
> +    pyhton3-fcntl \
> +    pyhton3-io \
> +    pyhton3-logging \
> +    pyhton3-misc \
> +    pyhton3-shell \
> +    pyhton3-threading \

pyhton3 -> python3 ?

Thanks,

Anuj

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

Re: [yocto] OpenSSH CVE-2023-38408

2023-07-27 Thread Anuj Mittal 
On Fri, 2023-07-28 at 10:46 +1200, Tom Isaacson wrote:
> I'm a Yocto noob so apologies if this is an obvious question.
> 
> I was just checking our usage of OpenSSH because of
> https://www.cvedetails.com/cve/CVE-2023-38408/ and it appears:
> 1. We're using a vulnerable version (9.3p1 on main, 8.9p1 on
> Kirkstone/LTS)
> 2. The ForwardAgent feature is enabled by default
> (
> https://git.yoctoproject.org/poky/tree/meta/recipes-connectivity/opens
> sh/openssh/ssh_config)
> 
> There doesn't seem to be a bug for this yet
> (https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=openssh).
> 
> So what's the process? Is this already being worked on somewhere or
> should I upgrade the version? If the latter should I do this on
> Kirkstone (which is what we're using) then main?
> 

Usually, the version should be upgraded in master and only the fix
backported in kirkstone.

Thanks,

Anuj

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

Re: [yocto][chromium] Need support to enable intel VAAPI with Chromium

2023-06-06 Thread Anuj Mittal 
On Wed, 2023-06-07 at 08:24 +0700, HuyK wrote:
> Hi all,
> 
> I am working on Intel J4125 platform with these meta layers:
>  - poky: master branch
>  - meta-intel: master branch
>  - meta-browser: master branch
> 
> 1/ I build chromium by chromium-ozone-wayland_111.0.5563.147.bb
> recipe with adding "use-vaapi" and "proprietary-codecs" to
> PACKAGECONFI in chromium-gn.inc 
> That chromium did not call intel VAAPI functions, but I see it
> loads iHD_drv_video.so at runtime.
> 
> 2/ Then I research to find this link about applying patches to
> support VAAPI in
> chromium https://aur.archlinux.org/packages/chromium-wayland-vaapi
>    + 0001-ozone-wayland-add-VA-API-support.patch
>    + vaapi-add-av1-support.patch
>    + use-oauth2-client-switches-as-default.patch
> This chromium loads iHD_drv_video.so and calls Intel VAAPI APIs;
> however, chromium reports these errors when I open to play an H264
> video so that HW Acceleration is not working 
> 
>  [13436:13436:0606/150528.263552:ERROR:vaapi_wrapper.cc(2399)]
> vaCreateSurfaces (import mode) failed, VA error: resource allocation
> failed
> [13436:13436:0606/150528.263789:ERROR:vaapi_picture_native_pixmap_ozo
> ne.cc(73)] Failed creating VASurface for NativePixmap
> [13436:13436:0606/150528.264843:ERROR:vaapi_wrapper.cc(2399)]
> vaCreateSurfaces (import mode) failed, VA error: resource allocation
> failed
> [13436:13436:0606/150528.265073:ERROR:vaapi_picture_native_pixmap_ozo
> ne.cc(73)] Failed creating VASurface for NativePixmap
> [13436:13436:0606/150528.265294:VERBOSE1:vaapi_video_decode_accelerat
> or.cc(142)] NotifyError(): Notifying of error 4

This doesn't look like complete error log. A complete log would have
helped.

> 
> So far, I could not find a solution to fix chromium errors and I am
> new to chromium, intel vaapi, libva debugging.
> 
> Please support how to debug the errors there or guidance on how to
> officially build chromium with intel VAAPI support in Yocto?

This doesn't seem to be Yocto related. This looks very similar so
please try the suggestions here:

https://github.com/intel/media-driver/issues/1498

Thanks,

Anuj

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

Re: [yocto] #kirkstone #systemd

2022-12-07 Thread Anuj Mittal 
On Wed, 2022-12-07 at 14:43 -0800, Gary Huband via
lists.yoctoproject.org wrote:
> I'm building an intel-corei7-64 image using meta-intel with systemd. 
> I need to modify /boot/loader/loader.conf and
> /boot/loader/entries/boot.conf.  I've tried using devtool modify for
> systemd, systemd-conf, systemd-boot, and systemd-bootconf, but the
> files were not in those recipes.  What recipe do I modify to change
> loader.conf and boot.conf?
> 

If you are using wic, you will need to modify your .wks file to supply
additional parameters as the files are generated by bootimg-efi plugin
in wic. The bootimg-efi plugin also allows supplying a custom boot cfg
file as well.

Thanks,

Anuj

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

Re: [yocto] [meta-yocto][dunfell][PATCH] linux-yocto/5.4: update genericx86* machines to v5.4.205

2022-09-05 Thread Anuj Mittal 
Hi Steve

I think this was sent to the wrong list. Can you include this in your
queue please?

Thanks,

Anuj

On Tue, 2022-08-16 at 20:20 +0530, Rajesh Dangi wrote:
> Signed-off-by: Rajesh Dangi 
> ---
>  .../recipes-kernel/linux/linux-yocto_5.4.bbappend | 8 --
> --
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-
> yocto_5.4.bbappend b/meta-yocto-bsp/recipes-kernel/linux/linux-
> yocto_5.4.bbappend
> index b2824cbb1d..219e788f47 100644
> --- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.4.bbappend
> +++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.4.bbappend
> @@ -7,8 +7,8 @@ KMACHINE_genericx86 ?= "common-pc"
>  KMACHINE_genericx86-64 ?= "common-pc-64"
>  KMACHINE_beaglebone-yocto ?= "beaglebone"
>  
> -SRCREV_machine_genericx86 ?=
> "e2020dbe2ccaef50d7e8f37a5bf08c68a006a064"
> -SRCREV_machine_genericx86-64 ?=
> "e2020dbe2ccaef50d7e8f37a5bf08c68a006a064"
> +SRCREV_machine_genericx86 ?=
> "8a59dfded81659402005acfb06fbb00b71c8ce86"
> +SRCREV_machine_genericx86-64 ?=
> "8a59dfded81659402005acfb06fbb00b71c8ce86"
>  SRCREV_machine_edgerouter ?=
> "706efec4c1e270ec5dda92275898cd465dfdc7dd"
>  SRCREV_machine_beaglebone-yocto ?=
> "706efec4c1e270ec5dda92275898cd465dfdc7dd"
>  
> @@ -17,7 +17,7 @@ COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
>  COMPATIBLE_MACHINE_edgerouter = "edgerouter"
>  COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
>  
> -LINUX_VERSION_genericx86 = "5.4.178"
> -LINUX_VERSION_genericx86-64 = "5.4.178"
> +LINUX_VERSION_genericx86 = "5.4.205"
> +LINUX_VERSION_genericx86-64 = "5.4.205"
>  LINUX_VERSION_edgerouter = "5.4.58"
>  LINUX_VERSION_beaglebone-yocto = "5.4.58"
> 
> 
> 


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

Re: [yocto] [Openembedded-architecture] Let's drop x86-x32 (was Re: [OE-core] [PATCH 05/51] rpm: update 4.17.0 -> 4.17.1)

2022-07-27 Thread Anuj Mittal 
On Wed, 2022-07-27 at 16:56 +0200, Alexander Kanavin wrote:
> On Wed, 20 Jul 2022 at 17:46, Alexander Kanavin via
> lists.yoctoproject.org
> 
> wrote:
> > 
> > On Wed, 20 Jul 2022 at 17:41, Mittal, Anuj 
> > wrote:
> > > I don't know if there are any Yocto users of it who might notice.
> > > 
> > > Instead of dropping the testing completely, may be we should
> > > switch to
> > > building/testing just the core-image-minimal image on autobuilder
> > > and
> > > keep at least some minimal support for now.
> > 
> > There's actually already a patch for that :)
> > https://lists.yoctoproject.org/g/yocto/message/56880
> 
> Which I just resent. Now we have confirmation from Intel that nobody
> minds reducing the scope of the AB test.
> 

It was just a personal opinion saying that I won't mind. If it's
needed, then someone would hopefully fix the issues.

Thanks,

Anuj

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

Re: [yocto] [Openembedded-architecture] Let's drop x86-x32 (was Re: [OE-core] [PATCH 05/51] rpm: update 4.17.0 -> 4.17.1)

2022-07-20 Thread Anuj Mittal 
On Wed, 2022-07-20 at 11:58 +0200, Alexander Kanavin wrote:
> On Wed, 20 Jul 2022 at 11:50, Ross Burton 
> wrote:
> > Also, Intel should get to have an opinion on this.  If they
> > actually care about x32 then they can help fix the issues, if they
> > don’t then we can easily switch to a platform that has support.
> 
> Ok, let's ask Intel, specifically Anuj :-)
> 
> Anuj, does Intel still care about x32, and would anyone notice if
> yocto drops x32 support from master branch?
> 

I don't know if there are any Yocto users of it who might notice.

Instead of dropping the testing completely, may be we should switch to
building/testing just the core-image-minimal image on autobuilder and
keep at least some minimal support for now.

Thanks,

Anuj

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

[yocto] [yocto-autobuilder2][PATCH] schedulers.py: dont schedule check-layer for honister

2022-05-31 Thread Anuj Mittal 
Honister is now EOL so remove the scheduled check.

Signed-off-by: Anuj Mittal 
---
 schedulers.py | 4 
 1 file changed, 4 deletions(-)

diff --git a/schedulers.py b/schedulers.py
index a11ce14..6d33969 100644
--- a/schedulers.py
+++ b/schedulers.py
@@ -417,10 +417,6 @@ 
schedulers.append(sched.Nightly(name='nightly-check-layer', branch='master', pro
 schedulers.append(sched.Nightly(name='nightly-metrics', branch='master', 
properties=parent_default_props('metrics'),
   builderNames=['metrics'], hour=7, minute=0))
 
-# Run check-layer-nightly twice a week for honister
-schedulers.append(sched.Nightly(name='nightly-check-layer-honister', 
properties=parent_default_props('check-layer-nightly', 'honister'),
-  builderNames=['check-layer-nightly'], dayOfWeek=[2, 5], 
hour=2, minute=0, codebases = {'' : {'branch' : 'honister'}}))
-
 # Run check-layer-nightly twice a week for kirkstone
 schedulers.append(sched.Nightly(name='nightly-check-layer-kirkstone', 
properties=parent_default_props('check-layer-nightly', 'kirkstone'),
   builderNames=['check-layer-nightly'], dayOfWeek=[0, 3], 
hour=2, minute=0, codebases = {'' : {'branch' : 'kirkstone'}}))
-- 
2.35.3


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

[yocto] [yocto-autobuilder2][PATCH 1/2] config.py: define workers for honister

2022-05-26 Thread Anuj Mittal 
Define the worker list for honister so we can test reliably now the
release support is ending.

Signed-off-by: Anuj Mittal 
---
 config.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/config.py b/config.py
index f36c273..e7539d9 100644
--- a/config.py
+++ b/config.py
@@ -152,6 +152,7 @@ all_workers = workers + workers_bringup + workers_buildperf 
+ workers_arm
 
 # Worker filtering for older releases
 workers_prev_releases = {
+"honister" : ("alma8", "centos7", "centos8", "debian8", "debian9", 
"debian10", "debian11", "fedora29", "fedora30", "fedora31", "fedora32", 
"fedora33", "fedora34", "fedora35", "opensuse150", "opensuse151", 
"opensuse152", "opensuse153", "ubuntu1604", "ubuntu1804", "ubuntu1904", 
"ubuntu2004", "ubuntu2110", "ubuntu2204", "perf-"),
 "hardknott" : ("centos7", "centos8", "debian8", "debian9", "debian10", 
"debian11", "fedora31", "fedora32", "fedora33", "fedora34", "opensuse152", 
"ubuntu1604", "ubuntu1804", "ubuntu2004", "perf-"),
 "gatesgarth" : ("centos7", "centos8", "debian8", "debian9", "debian10", 
"fedora30", "fedora31", "fedora32", "opensuse150", "opensuse151", 
"opensuse152", "ubuntu1604", "ubuntu1804", "ubuntu1904", "ubuntu2004", "perf-"),
 "dunfell" : (""alma8", centos7", "centos8", "debian8", "debian9", 
"debian10", "debian11", "fedora29", "fedora30", "fedora31", "fedora32", 
"fedora33", "fedora34", "fedora35", "opensuse150", "opensuse151", 
"opensuse152", "opensuse153", "ubuntu1604", "ubuntu1804", "ubuntu1904", 
"ubuntu2004", "perf-"),
-- 
2.35.3


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

[yocto] [yocto-autobuilder2][PATCH 2/2] config.py: fix quotes in workers_prev_releases list

2022-05-26 Thread Anuj Mittal 
Signed-off-by: Anuj Mittal 
---
 config.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config.py b/config.py
index e7539d9..c3c21f1 100644
--- a/config.py
+++ b/config.py
@@ -155,7 +155,7 @@ workers_prev_releases = {
 "honister" : ("alma8", "centos7", "centos8", "debian8", "debian9", 
"debian10", "debian11", "fedora29", "fedora30", "fedora31", "fedora32", 
"fedora33", "fedora34", "fedora35", "opensuse150", "opensuse151", 
"opensuse152", "opensuse153", "ubuntu1604", "ubuntu1804", "ubuntu1904", 
"ubuntu2004", "ubuntu2110", "ubuntu2204", "perf-"),
 "hardknott" : ("centos7", "centos8", "debian8", "debian9", "debian10", 
"debian11", "fedora31", "fedora32", "fedora33", "fedora34", "opensuse152", 
"ubuntu1604", "ubuntu1804", "ubuntu2004", "perf-"),
 "gatesgarth" : ("centos7", "centos8", "debian8", "debian9", "debian10", 
"fedora30", "fedora31", "fedora32", "opensuse150", "opensuse151", 
"opensuse152", "ubuntu1604", "ubuntu1804", "ubuntu1904", "ubuntu2004", "perf-"),
-"dunfell" : (""alma8", centos7", "centos8", "debian8", "debian9", 
"debian10", "debian11", "fedora29", "fedora30", "fedora31", "fedora32", 
"fedora33", "fedora34", "fedora35", "opensuse150", "opensuse151", 
"opensuse152", "opensuse153", "ubuntu1604", "ubuntu1804", "ubuntu1904", 
"ubuntu2004", "perf-"),
+"dunfell" : ("alma8", "centos7", "centos8", "debian8", "debian9", 
"debian10", "debian11", "fedora29", "fedora30", "fedora31", "fedora32", 
"fedora33", "fedora34", "fedora35", "opensuse150", "opensuse151", 
"opensuse152", "opensuse153", "ubuntu1604", "ubuntu1804", "ubuntu1904", 
"ubuntu2004", "perf-"),
 "zeus" : ("centos7", "debian8", "debian9", "debian10", "fedora28", 
"fedora29", "fedora30", "opensuse150", "opensuse151", "ubuntu1604", 
"ubuntu1804", "ubuntu1904", "perf-"),
 "warrior" : ("centos7", "debian8", "debian9", "debian10", "fedora28", 
"fedora29", "fedora30", "opensuse150", "opensuse151", "ubuntu1604", 
"ubuntu1804", "ubuntu1904", "perf-"),
 "thud" : ("centos7", "debian8", "debian9", "debian10", "fedora28", 
"fedora29", "fedora30", "opensuse150", "opensuse151", "ubuntu1604", 
"ubuntu1804", "ubuntu1904", "perf-"),
-- 
2.35.3


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

Re: [yocto] CVE metrics tracking from the autobuilder

2022-05-25 Thread Anuj Mittal 
Hi Richard,

On Wed, 2022-05-25 at 14:30 +0100, Richard Purdie wrote:
> I'm happy to say that automatic CVE metric tracking is now on the
> autobuilder and automatically feeding to:
> 
> https://autobuilder.yocto.io/pub/non-release/patchmetrics/
> 
> and the git repository that backs it:
> 
> https://git.yoctoproject.org/yocto-metrics/log/

This is very nice.

> 
> This is working for dunfell/kirkstone/master. It is enabled for
> honister but doesn't work since the json CVE output for honister
> isn't
> there.
> 
> Not sure if we want to add the json CVE output to honister to enable
> that for the short time that release has left?

Yeah, there is only a week left and I wasn't planning to take those
patches in my final pull request.

Thanks,

Anuj


> 
> I plan to run the autobuilder job powering this nightly.
> 
> Currently it adds a json file for each run into the yocto-metrics
> repository. These are 6MB each though so we're going to get into
> silly
> amounts of data rather quickly so I may have to adjust it to just
> write
> the latest. It would also help the size to use tabs instead of spaces
> for indentation.
> 
> The autobuilder job currently throws warnings but I think Ross said
> he'd send a patch to allow that to be configurable.
> 
> Also, this doesn't send the CVE emails Steve currently sends. It
> would
> be possible to add, I'm hoping someone might like to send some
> patches!
> 
> Cheers,
> 
> Richard
> 
> 
> 
> 
> 


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

Re: [yocto] ERROR: cp: cannot stat 'Module.symvers': No such file or directory

2022-05-18 Thread Anuj Mittal 
On Wed, 2022-05-18 at 11:50 +, Duda, Alexander wrote:
> Hello yocto users,
>  
> I keep getting the following error, 
> Does someone have a hint where I can look to solve this issue?
>  
> ERROR: linux-fslc-5.15-r0 do_shared_workdir: Execution of
> '/zeus/build/tmp/work/ -poky-linux/linux-fslc/5.15-
> r0/temp/run.do_shared_workdir.58919' failed with exit code 1:
> cp: cannot stat 'Module.symvers': No such file or directory
> WARNING: exit code 1 from a shell command.
>  
> ERROR: Logfile of failure stored in: /zeus/build/tmp/work/ -poky-
> linux/linux-fslc/5.15-r0/temp/log.do_shared_workdir.58919
> Log data follows:
> | DEBUG: Executing shell function do_shared_workdir
> | cp: cannot stat 'Module.symvers': No such file or directory
> | WARNING: exit code 1 from a shell command.
> | ERROR: Execution of '/zeus/build/tmp/work/ -poky-linux/linux-
> fslc/5.15-r0/temp/run.do_shared_workdir.58919' failed with exit code
> 1:
> | cp: cannot stat 'Module.symvers': No such file or directory
> | WARNING: exit code 1 from a shell command.
>  

Do you have this change:

https://git.yoctoproject.org/poky/commit/?h=zeus&id=05043a26cc297ed9834055678ac699e20e2f16d5

Thanks,

Anuj

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

Re: [yocto] [ANNOUNCEMENT] Yocto Project 3.3.6 (hardknott-25.0.6) is Released

2022-04-27 Thread Anuj Mittal 
Thanks Chee Yang. 

This is the last hardknott release and the branch will no longer be
actively maintained.

Thanks,

Anuj

On Thu, 2022-04-28 at 02:16 +, Lee Chee Yang wrote:
> Hello
>  
> We are pleased to announce the Yocto Project 3.3.6 (hardknott-25.0.6)
> Release is now available for download.
>  
> http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.6/poky-hardknott-25.0.6.tar.bz2
> http://mirrors.kernel.org/yocto/yocto/yocto-3.3.6/poky-hardknott-25.0.6.tar.bz2
>  
> A gpg signed version of these release notes is available at:
>  
> http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.6/RELEASENOTES
>  
> Full Test Report:
>  
> http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.6/testreport.txt
>  
> Thank you for everyone's contributions to this release.
>  
> Chee Yang Lee 
> Chee Yang Lee chee.yang@intel.com
> Yocto Project Build and Release
>  
>  
> - --
> yocto-3.3.6 Release Notes
> - --
>  
>  
> - --
> Repositories/Downloads
> - --
>  
> Repository Name: poky
> Repository Location: https://git.yoctoproject.org/git/poky
> Branch: hardknott
> Tag: yocto-3.3.6
> Git Revision: eee9fba7b4d5d7a268a495688039027390894e6d
> Release Artefact: poky-hardknott-25.0.6
> sha: a0d015fb81b3be476faf46ebb9c968b073c070e6abbc3d3074897983dd1248cc
> Download Locations:
> http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.6/poky-hardknott-25.0.6.tar.bz2
> http://mirrors.kernel.org/yocto/yocto/yocto-3.3.6/poky-hardknott-25.0.6.tar.bz2
>  
> Repository Name: openembedded-core
> Repository Location: https://git.openembedded.org/openembedded-core
> Branch: hardknott
> Tag: yocto-3.3.6
> Git Revision: fbbb689c8df7f82644b8a9bc5bb6884bc6516660
> Release Artefact: oecore-hardknott-25.0.6
> sha: b60ded848198fd25ca2b5f53c9fc6be5c07c6ab1783641c8fe5bc4bbf092b861
> Download Locations:
> http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.6/oecore-hardknott-25.0.6.tar.bz2
> http://mirrors.kernel.org/yocto/yocto/yocto-3.3.6/oecore-hardknott-25.0.6.tar.bz2
>  
> Repository Name: meta-mingw
> Repository Location: https://git.yoctoproject.org/git/meta-mingw
> Branch: hardknott
> Tag: yocto-3.3.6
> Git Revision: 422b96cb2b6116442be1f40dfb5bd77447d1219e
> Release Artefact: meta-mingw-hardknott-25.0.6
> sha: 80b7e7b6da68315fb74ba40c3f668deac5dc14be04be60c8a345807d9149994a
> Download Locations:
> http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.6/meta-mingw-hardknott-25.0.6.tar.bz2
> http://mirrors.kernel.org/yocto/yocto/yocto-3.3.6/meta-mingw-hardknott-25.0.6.tar.bz2
>  
>  
> Repository Name: meta-gplv2
> Repository Location: https://git.yoctoproject.org/git/meta-gplv2
> Branch: hardknott
> Tag: yocto-3.3.6
> Git Revision: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f
> Release Artefact: meta-gplv2-hardknott-25.0.6
> sha: ea863d84ef79aab27ad3533d0d6f0aa87eb6f5e6fe2b29a2756eaf5620a9dd00
> Download Locations:
> http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.6/meta-gplv2-hardknott-25.0.6.tar.bz2
> http://mirrors.kernel.org/yocto/yocto/yocto-3.3.6/meta-gplv2-hardknott-25.0.6.tar.bz2
>  
> Repository Name: bitbake
> Repository Location: https://git.openembedded.org/bitbake
> Branch: hardknott
> Tag: yocto-3.3.6
> Git Revision: d01d8326331cfe59208674cfc53aa26c0028b313
> Release Artefact: bitbake-hardknott-25.0.6
> sha: 2a85c71c0243f6da0abf829b391f2c01b049d8f3cb4b53cf903facc251b92682
> Download Locations:
> http://downloads.yoctoproject.org/releases/yocto/yocto-3.3.6/bitbake-hardknott-25.0.6.tar.bz2
> http://mirrors.kernel.org/yocto/yocto/yocto-3.3.6/bitbake-hardknott-25.0.6.tar.bz2
>  
> Repository Name: yocto-docs
> Repository Location: https://git.yoctoproject.org/git/yocto-docs
> Branch: hardknott
> Tag: yocto-3.3.6
> Git Revision: f462982ddb6e32052217d44c0c44e8a4df115589
>  
>  
> - ---
> Known Issues
> - ---
> N/A
>  
>  
> - ---
> Security Fixes
> - ---
> zlib: backport the fix for CVE-2018-25032
> python3-numpy: fix CVE-2021-41496
> epiphany: fix CVE-2021-45085 CVE-2021-45086 CVE-2021-45087 CVE-2021-
> 45088
> flac: fix CVE-2021-0561
> libxml2: Fix CVE-2022-23308
> expat: fix CVE-2022-25236
> expat: fix CVE-2022-25235
> ghostscript: fix CVE-2021-45949
> expat: fix CVE-2022-23990
> virglrenderer: fix CVE-2022-0135 and -0175
>  
>  
> - ---
> Fixes
> - ---
> asciidoc: update git repository
> bitbake: server/process: Disable gc around critical section
> bitbake: server/xmlrpcserver: Add missing xmlrpcclient import
> bitbake: tests/fetch: Handle upstream master -> main branch change
> bitbake: toaster: Fix IMAGE_INSTALL issues with _append vs :append
> bitbake: toaster: fixtures: gatesgarth -> hardknott
> ccache: upgrade 4.2 -> 4.2.1
> devtool: deploy-target: Remove stripped binaries in pseudo context
> docs: fix hardcoded link warning messages
> documentation: prepare for 3.3.5 release
> documentation: prepare

[yocto] [yocto-autobuilder-helper][hardknott 3/3] shared-repos: Use tar instead of rsync for speed

2022-02-28 Thread Anuj Mittal 
From: Richard Purdie 

The rysnc of 20,000 files (650MB) onto the nas is slow taking ~3 minutes
at idle and worse at load. This is due to the number of files which
is a pain point for NFS. This piece of the build is also a bottleneck
since the rest of a build depends on it happening.

If we switch to zstd compressed tar, it takes 2.49s. Other compression
methods were much slower but zstd seems 'accptable' and speeds things
up too.

Signed-off-by: Richard Purdie 
(cherry picked from commit aff49e938ee34e1fc5a2954e3e22a4ca1ae9ac7b)
Signed-off-by: Anuj Mittal 
---
 scripts/prepare-shared-repos | 4 ++--
 scripts/send-qa-email| 6 --
 scripts/shared-repo-unpack   | 9 ++---
 3 files changed, 12 insertions(+), 7 deletions(-)

diff --git a/scripts/prepare-shared-repos b/scripts/prepare-shared-repos
index c221e69..a5bc0da 100755
--- a/scripts/prepare-shared-repos
+++ b/scripts/prepare-shared-repos
@@ -39,5 +39,5 @@ with tempfile.TemporaryDirectory(prefix="shared-repo-temp-", 
dir="/home/pokybuil
 if args.publish_dir:
 utils.publishrepo(tempdir, repo, args.publish_dir)
 
-utils.printheader("Running rsync")
-subprocess.check_call("rsync -a " + tempdir + "/* " + args.sharedsrcdir, 
shell=True)
+utils.printheader("Creating shared src tarball")
+subprocess.check_call("tar -I zstd -cf " + args.sharedsrcdir.rstrip("/") + 
".tar.zst ./*", shell=True, cwd=tempdir)
diff --git a/scripts/send-qa-email b/scripts/send-qa-email
index 1b69307..bc594df 100755
--- a/scripts/send-qa-email
+++ b/scripts/send-qa-email
@@ -45,9 +45,11 @@ buildtoolsdir = os.path.dirname(args.repojson) + 
"/build/buildtools"
 if os.path.exists(buildtoolsdir):
 utils.enable_buildtools_tarball(buildtoolsdir)
 
+repodir = os.path.dirname(args.repojson) + "/build/repos"
+
 if 'poky' in repos and os.path.exists(resulttool) and args.results_dir:
 # Need the finalised revisions (not 'HEAD')
-targetrepodir = "%s/poky" % (args.sharedrepodir)
+targetrepodir = "%s/poky" % (repodir)
 revision = subprocess.check_output(["git", "rev-parse", "HEAD"], 
cwd=targetrepodir).decode('utf-8').strip()
 branch = repos['poky']['branch']
 repo = repos['poky']['url']
@@ -116,7 +118,7 @@ if args.send.lower() != 'true' or not args.publish_dir or 
not args.release:
 buildhashes = ""
 for repo in sorted(repos.keys()):
 # Need the finalised revisions (not 'HEAD')
-targetrepodir = "%s/%s" % (args.sharedrepodir, repo)
+targetrepodir = "%s/%s" % (repodir, repo)
 revision = subprocess.check_output(["git", "rev-parse", "HEAD"], 
cwd=targetrepodir).decode('utf-8').strip()
 buildhashes += "%s: %s\n" % (repo, revision)
 
diff --git a/scripts/shared-repo-unpack b/scripts/shared-repo-unpack
index f08efa8..f7f87af 100755
--- a/scripts/shared-repo-unpack
+++ b/scripts/shared-repo-unpack
@@ -50,11 +50,14 @@ needrepos_baseddirs = [r.split('/')[0] for r in needrepos]
 for repo in sorted(repos.keys()):
 if repo not in needrepos_baseddirs:
 continue
-targetrepodir = "%s/%s" % (targetsubdir, repo)
 if args.cache_dir:
 utils.printheader("Copying in repo %s" % repo)
-utils.mkdir(targetrepodir)
-subprocess.check_call(["rsync", "-a", "%s/%s" % (args.cache_dir, 
repo), targetsubdir])
+utils.mkdir(targetsubdir)
+if args.target in ["a-full", "a-quick"]:
+# full/quick need all repo data due to send-qa-email
+subprocess.check_call(["tar", "-I", "zstd", "-C", targetsubdir, 
"-xf", "%s.tar.zst" % args.cache_dir])
+else:
+subprocess.check_call(["tar", "-I", "zstd", "-C", targetsubdir, 
"-xf", "%s.tar.zst" % args.cache_dir, "./" + repo])
 else:
 utils.printheader("Fetching repo %s" % repo)
 utils.fetchgitrepo(targetsubdir, repo, repos[repo], stashdir)
-- 
2.35.1


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

[yocto] [yocto-autobuilder-helper][hardknott 2/3] prepare-shared-repos: Make it clear when rsync starts in logs

2022-02-28 Thread Anuj Mittal 
From: Richard Purdie 

Signed-off-by: Richard Purdie 
(cherry picked from commit 8e996a95a8902b40380dd477ecb606cc969cdee9)
Signed-off-by: Anuj Mittal 
---
 scripts/prepare-shared-repos | 1 +
 1 file changed, 1 insertion(+)

diff --git a/scripts/prepare-shared-repos b/scripts/prepare-shared-repos
index 1573f85..c221e69 100755
--- a/scripts/prepare-shared-repos
+++ b/scripts/prepare-shared-repos
@@ -39,4 +39,5 @@ with tempfile.TemporaryDirectory(prefix="shared-repo-temp-", 
dir="/home/pokybuil
 if args.publish_dir:
 utils.publishrepo(tempdir, repo, args.publish_dir)
 
+utils.printheader("Running rsync")
 subprocess.check_call("rsync -a " + tempdir + "/* " + args.sharedsrcdir, 
shell=True)
-- 
2.35.1


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

[yocto] [yocto-autobuilder-helper][hardknott 1/3] scripts/prepare-shared-repos: Use tmpfs for speed

2022-02-28 Thread Anuj Mittal 
From: Richard Purdie 

Signed-off-by: Richard Purdie 
(cherry picked from commit 298a10575851d501204fe1ee0d1dcbcec37a66cd)
Signed-off-by: Anuj Mittal 
---
 scripts/prepare-shared-repos | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/prepare-shared-repos b/scripts/prepare-shared-repos
index 8400d09..1573f85 100755
--- a/scripts/prepare-shared-repos
+++ b/scripts/prepare-shared-repos
@@ -32,7 +32,7 @@ with open(args.repojson) as f:
 
 stashdir = utils.getconfig("REPO_STASH_DIR", ourconfig)
 
-with tempfile.TemporaryDirectory(prefix="shared-repo-temp-", dir="/tmp") as 
tempdir:
+with tempfile.TemporaryDirectory(prefix="shared-repo-temp-", 
dir="/home/pokybuild/tmp") as tempdir:
 for repo in sorted(repos.keys()):
 utils.printheader("Intially fetching repo %s" % repo)
 utils.fetchgitrepo(tempdir, repo, repos[repo], stashdir)
-- 
2.35.1


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

Re: [yocto] [OE-core] Yocto Project Status WW08`22

2022-02-27 Thread Anuj Mittal 
On Sun, 2022-02-27 at 07:28 -0800, Armin Kuster wrote:
> I see there is an April release of Hardknott.  Is that the last
> official 
> Hardknott release from the Yocto Project?

There's going to be a 3.3.6 as well and that is going to be the last.
From this status email:

  * YP 3.3.6 build date 2022/03/28
  * YP 3.3.6 Release date 2022/04/08

Thanks,

Anuj

> 
> -armin
> 
> On 2/22/22 07:54, Stephen Jolley wrote:
> > 
> > Current Dev Position: YP 3.5 M4
> > 
> > Next Deadline: 4th April. 2022 YP 3.5 M4 build
> > 
> > Next Team Meetings:
> > 
> >   * Bug Triage meeting Thursday Feb. 24th 7:30 am PDT
> >    
> > (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09
> >    
> > )
> >   * Monthly Project Meeting Tuesday Mar. 1st at 8 am PDT
> >    
> > (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
> >    
> > )
> >     
> >   * Weekly Engineering Sync Tuesday Feb. 22nd at 8 am PDT
> >    
> > (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
> >    
> > )
> >     
> >   * Twitch - See https://www.twitch.tv/theyoctojester
> > 
> > Key Status/Updates:
> > 
> >   * We are now at feature freeze for 3.5, our next LTS release
> >   * YP 3.1.14 and YP 3.2.4 were released
> >   * YP 3.3.5 is in QA
> >   * After a last minute push, the base set of inclusive language
> >     changes have merged. There is a conversion script which can be
> > run
> >     to convert layers. Not all changes needed have been written yet
> >     but enough are present to allow the conversion process to
> > start.
> >   * There were also changes to convert LICENSE fields to use SPDX
> >     identifiers and there is a second conversion script for this
> > that
> >     can be used.
> >   * We have updated the core layer series name to kirkstone and
> > other
> >     layers will now need to update to confirm compatibility with
> >     kirkstone.
> >   * There is a patchset to update python’s build processes to use
> > the
> >     upstream preferred wheel approach which would aid support of
> >     python over the next few years. It is late in the cycle for
> > this
> >     kind of change but we will give this series a few days of
> > testing
> >     to make a decision and welcome user feedback either way on
> > these
> >     changes.
> >   * As such, the M3 release build will likely not happen until
> > early
> >     next week.
> >   * The autobuilder infrastructure is planned to be offline 26-28th
> >     February for a data center move. Public services like the
> > website,
> >     wiki and git servers will remain live but the git backend
> >     (push.yoctoproject.org) will be offline, as will the downloads
> > and
> >     sstate services and the autobuilder/NAS.
> >   * Capacity has been improved on the sstate server which was
> > causing
> >     intermittent timeout issues for downloads.
> >   * Intermittent issues continue to be at record high levels and
> > help
> >     is very much welcome in trying to resolve them. You can see the
> >     list of failures we’re continuing to see by searching for the
> >     “AB-INT” tag in bugzilla:
> >    
> > https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT
> >    
> > 
> > 
> > In particular, we’re struggling to understand the intermittent
> > network 
> > issue with external hosts we’re seeing very occasionally.
> > 
> > Ways to contribute:
> > 
> >   * There are bugs identified as possible for newcomers to the
> >     project: https://wiki.yoctoproject.org/wiki/Newcomers
> >     
> >   * There are bugs that are currently unassigned for YP 3.5. See:
> >    
> > https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.5_Unassigned_Enhancements.2FBugs
> >    
> >  > gned_Enhancements.2FBugs>
> >   * We’d welcome new maintainers for recipes in OE-Core. Please see
> >     the list at:
> >    
> > http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc
> >    
> >  > clude/maintainers.inc>
> >     and discuss with the existing maintainer, or ask on the OE-Core
> >     mailing list. We will likely move a chunk of these to
> > “Unassigned”
> >     soon to help facilitate this.
> >   * Help us resolve CVE issues: CVE metrics
> >    
> >  > ezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubch
> > art?oid=1993375488&format=interactive>
> > 
> > 
> > YP 3.5 Milestone Dates:
> > 
> >   * YP 3.5 M3 build date 2022/02/21
> >   * YP 3.5 M3

Re: [yocto] [tsc] 3.4.2 rc1 QA

2022-02-14 Thread Anuj Mittal 
On Thu, 2022-02-10 at 16:32 +, Richard Purdie wrote:
> On Thu, 2022-02-10 at 16:30 +, Raj, Khem wrote:
> > Can we then keep meta-agl for LTS and master only ? as it seems
> > that’s what it
> > is going to support
> 
> Yes, I got a reply from Scott/Jan-Simon saying to not test this on
> honister
> going forward so I'll make that change. That shouldn't therefore
> block this
> going into QA, just a question of the sstate issues.
> 
> If we did block on those, I'm not sure when we'd have them fixed by
> :/

I think we should not block the release because of this issue.

Thanks,

Anuj


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

[yocto] [yocto-autobuilder2][PATCH] config.py: enable debian11 for hardknott

2022-01-18 Thread Anuj Mittal 
Signed-off-by: Anuj Mittal 
---
 config.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config.py b/config.py
index 4c0b83b..0f99557 100644
--- a/config.py
+++ b/config.py
@@ -149,7 +149,7 @@ all_workers = workers + workers_bringup + workers_buildperf 
+ workers_arm
 
 # Worker filtering for older releases
 workers_prev_releases = {
-"hardknott" : ("centos7", "centos8", "debian8", "debian9", "debian10", 
"fedora31", "fedora32", "fedora33", "fedora34", "opensuse152", "ubuntu1604", 
"ubuntu1804", "ubuntu2004", "perf-"),
+"hardknott" : ("centos7", "centos8", "debian8", "debian9", "debian10", 
"debian11", "fedora31", "fedora32", "fedora33", "fedora34", "opensuse152", 
"ubuntu1604", "ubuntu1804", "ubuntu2004", "perf-"),
 "gatesgarth" : ("centos7", "centos8", "debian8", "debian9", "debian10", 
"fedora30", "fedora31", "fedora32", "opensuse150", "opensuse151", 
"opensuse152", "ubuntu1604", "ubuntu1804", "ubuntu1904", "ubuntu2004", "perf-"),
 "dunfell" : ("centos7", "centos8", "debian8", "debian9", "debian10", 
"debian11", "fedora29", "fedora30", "fedora31", "fedora32", "fedora33", 
"fedora34", "opensuse150", "opensuse151", "opensuse152", "ubuntu1604", 
"ubuntu1804", "ubuntu1904", "ubuntu2004", "perf-"),
 "zeus" : ("centos7", "debian8", "debian9", "debian10", "fedora28", 
"fedora29", "fedora30", "opensuse150", "opensuse151", "ubuntu1604", 
"ubuntu1804", "ubuntu1904", "perf-"),
-- 
2.34.1


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

[yocto] [yocto-autobuilder2][PATCH] config.py: enable fedora34 for hardknott

2022-01-03 Thread Anuj Mittal 
Signed-off-by: Anuj Mittal 
---
 config.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config.py b/config.py
index 5b21095..ea042c6 100644
--- a/config.py
+++ b/config.py
@@ -147,7 +147,7 @@ all_workers = workers + workers_bringup + workers_buildperf 
+ workers_arm
 
 # Worker filtering for older releases
 workers_prev_releases = {
-"hardknott" : ("centos7", "centos8", "debian8", "debian9", "debian10", 
"fedora31", "fedora32", "fedora33", "opensuse152", "ubuntu1604", "ubuntu1804", 
"ubuntu2004", "perf-"),
+"hardknott" : ("centos7", "centos8", "debian8", "debian9", "debian10", 
"fedora31", "fedora32", "fedora33", "fedora34", "opensuse152", "ubuntu1604", 
"ubuntu1804", "ubuntu2004", "perf-"),
 "gatesgarth" : ("centos7", "centos8", "debian8", "debian9", "debian10", 
"fedora30", "fedora31", "fedora32", "opensuse150", "opensuse151", 
"opensuse152", "ubuntu1604", "ubuntu1804", "ubuntu1904", "ubuntu2004", "perf-"),
 "dunfell" : ("centos7", "centos8", "debian8", "debian9", "debian10", 
"debian11", "fedora29", "fedora30", "fedora31", "fedora32", "fedora33", 
"fedora34", "opensuse150", "opensuse151", "opensuse152", "ubuntu1604", 
"ubuntu1804", "ubuntu1904", "ubuntu2004", "perf-"),
 "zeus" : ("centos7", "debian8", "debian9", "debian10", "fedora28", 
"fedora29", "fedora30", "opensuse150", "opensuse151", "ubuntu1604", 
"ubuntu1804", "ubuntu1904", "perf-"),
-- 
2.33.1


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

Re: [yocto] meta-intel / zeus

2021-11-15 Thread Anuj Mittal 
On Mon, 2021-11-15 at 17:32 +, Monsees, Steven C (US) via
lists.yoctoproject.org wrote:
>  
> Recently I built in base intel NEO driver components under meta-intel…
> It appears I require a little more than just NEO.
>  
> Does yocto support the khronos icd loader ?, 
> Is there something I can build/enable tp provide this ?

meta-oe has recipes for both Khronos loader as well as ocl-icd that NEO
prefers.

Layerindex can also be used to check these sort of things:

https://layers.openembedded.org/layerindex/branch/master/recipes/?q=icd


Thanks,

Anuj

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

Re: [yocto] yocto preempt-rt

2021-11-02 Thread Anuj Mittal 
On Tue, 2021-11-02 at 17:34 +0100, Leon Woestenberg wrote:
> On Tue, Nov 2, 2021 at 5:26 PM Bruce Ashfield
>  wrote:
> > 
> > Correct.
> > 
> > The rt patches are already integrated on the branches that that
> > recipe will build out of the linux-yocto repository.
> > 
> And adding to that, besides the Yocto maintained kernel,  meta-intel
> has it's own kernel GIT repo/branch for the kernel and -rt kernel
> maintained by Intel.

Right, you can either build linux-yocto-rt or the Intel version with
linux-intel-rt. linux-intel tree might have some platform specific
patches that have either been backported or not upstreamed yet.

The branch & version information is available in the recipe.

Thanks,

Anuj

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

[yocto] [yocto-autobuilder-helper][PATCH] config.json: add honister to buildhistory

2021-10-25 Thread Anuj Mittal 
Signed-off-by: Anuj Mittal 
---
 config.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config.json b/config.json
index 0c7f711..0788123 100644
--- a/config.json
+++ b/config.json
@@ -5,7 +5,7 @@
 
 "BUILD_HISTORY_DIR" : "buildhistory",
 "BUILD_HISTORY_REPO" : 
"ssh://g...@push.yoctoproject.org/poky-buildhistory",
-"BUILD_HISTORY_DIRECTPUSH" : ["poky:morty", "poky:pyro", "poky:rocko", 
"poky:sumo", "poky:thud", "poky:warrior", "poky:zeus", "poky:dunfell", 
"poky:gatesgarth", "poky:hardknott", "poky:master"],
+"BUILD_HISTORY_DIRECTPUSH" : ["poky:morty", "poky:pyro", "poky:rocko", 
"poky:sumo", "poky:thud", "poky:warrior", "poky:zeus", "poky:dunfell", 
"poky:gatesgarth", "poky:hardknott", "poky:honister", "poky:master"],
 "BUILD_HISTORY_FORKPUSH" : {"poky-contrib:ross/mut" : "poky:master", 
"poky:master-next" : "poky:master"},
 
 "BUILDTOOLS_URL_TEMPLOCAL" : 
"/srv/autobuilder/autobuilder.yoctoproject.org/pub/non-release/20210214-8/buildtools/x86_64-buildtools-extended-nativesdk-standalone-3.2+snapshot-7d38cc8e749aedb8435ee71847e04b353cca541d.sh",
-- 
2.31.1


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

[yocto] [hardknott][yocto-autobuilder-helper][PATCH] config.json: set max load in PARALLEL_MAKE

2021-10-25 Thread Anuj Mittal 
From: Trevor Gamblin 

Add "-l 52" to PARALLEL_MAKE in config.json to limit Make and Ninja
builds based on the detected system load. With this option added, if
either tool has at least one job running and detects that the system
load exceeds the given value, it will wait until either the system load
average drops below that limit, or until all other jobs are finished
before starting additional jobs.

Since most autobuilder machines have 56 cores, this should help keep the
system from being overloaded during builds.

Reference: https://www.gnu.org/software/make/manual/html_node/Parallel.html

Signed-off-by: Trevor Gamblin 
Signed-off-by: Richard Purdie 
(cherry picked from commit 5c5fc7bcd221427d34bbac80c9bad315fb6de4df)
Signed-off-by: Anuj Mittal 
---
 config.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config.json b/config.json
index 33d36ad..d397365 100644
--- a/config.json
+++ b/config.json
@@ -43,7 +43,7 @@
 "PREMIRRORS = ''",
 "BB_GENERATE_MIRROR_TARBALLS = '1'",
 "BB_NUMBER_THREADS = '16'",
-"PARALLEL_MAKE = '-j 16'",
+"PARALLEL_MAKE = '-j 16 -l 52'",
 "XZ_MEMLIMIT = '5%'",
 "XZ_THREADS = '8'",
 "BB_TASK_NICE_LEVEL = '5'",
-- 
2.31.1


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

Re: [yocto] #zeus meta-intel

2021-10-13 Thread Anuj Mittal 
> llvm::cl::parser > std::char_traits, std::allocator > >
> > > ::opt > llvm::cl::desc const&, llvm::cl::initializer const&)':
> > /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
> > default/tmp/work/x86_64-linux/intel-graphics-compiler-
> > native/1.0.11-
> > r0/recipe-sysroot-
> > native/usr/include/llvm/Support/CommandLine.h:1407:
> > undefined reference to `vtable for
> > llvm::cl::opt > std::char_traits, 
> > std::allocator >, false, 
> > llvm::cl::parser > std::char_traits, std::allocator > > >'
> > /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
> > pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > `llvm::cl::parser > std::char_traits, std::allocator >
> > > ::parser(llvm::cl::Option&)':
> > /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
> > default/tmp/work/x86_64-linux/intel-graphics-compiler-
> > native/1.0.11-
> > r0/recipe-sysroot-
> > native/usr/include/llvm/Support/CommandLine.h:1072:
> > undefined reference to `vtable for
> > llvm::cl::parser > std::char_traits, std::allocator > >'
> > /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
> > pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > `llvm::cl::opt > std::char_traits, std::allocator >, false, 
> > llvm::cl::parser > std::char_traits, std::allocator > > >::~opt()':
> > /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
> > default/tmp/work/x86_64-linux/intel-graphics-compiler-
> > native/1.0.11-
> > r0/recipe-sysroot-
> > native/usr/include/llvm/Support/CommandLine.h:1331:
> > undefined reference to `vtable for
> > llvm::cl::opt > std::char_traits, 
> > std::allocator >, false, 
> > llvm::cl::parser > std::char_traits, std::allocator > > >'
> > /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
> > pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > `llvm::cl::OptionValue > std::char_traits, std::allocator > >::OptionValue()':
> > /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
> > default/tmp/work/x86_64-linux/intel-graphics-compiler-
> > native/1.0.11-
> > r0/recipe-sysroot-
> > native/usr/include/llvm/Support/CommandLine.h:601:
> > undefined reference to `vtable for
> > llvm::cl::OptionValue > std::char_traits, std::allocator > >'
> > /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
> > pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > `llvm::cl::opt > std::char_traits, std::allocator >, false, 
> > llvm::cl::parser > std::char_traits, std::allocator > > >::opt > llvm::cl::desc>(char const (&) [9], llvm::cl::desc const&)':
> > /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
> > default/tmp/work/x86_64-linux/intel-graphics-compiler-
> > native/1.0.11-
> > r0/recipe-sysroot-
> > native/usr/include/llvm/Support/CommandLine.h:1407:
> > undefined reference to `vtable for
> > llvm::cl::opt > std::char_traits, 
> > std::allocator >, false, 
> > llvm::cl::parser > std::char_traits, std::allocator > > >'
> > /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
> > pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
> > `llvm::cl::parser > std::char_traits, std::allocator >
> > > ::parser(llvm::cl::Option&)':
> > /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
> > default/tmp/work/x86_64-linux/intel-graphics-compiler-
> > native/1.0.11-
> > r0/recipe-sysroot-
> > native/usr/include/llvm/Support/CommandLine.h:1072:
> > undefined reference to `vtable for
> > llvm::cl::parser > std::char_traits, std::allocator > >'
> > collect2: error: ld returned 1 exit status
> > 
> > -Original Message-
> > From: yocto@lists.yoctoproject.org 
> > On 
> > Behalf Of Anuj Mittal
> > Sent: Tuesday, October 12, 2021 10:43 AM
> > To: Monsees, Steven C (US) ; 
> > yocto@lists.yoctoproject.org
> > Subject: Re: [yocto] #zeus meta-intel
> > 
> > External Email Alert
> > 
> > network.
> > 
> > Please treat the email with caution, especially if you are
> > requested 
> > to click on a link, decrypt/open an attachment, or enable macros. 
> > For 
> > further information on how to spot phishing, access “Cybersecurity 
> > OneSpace Page” and report phishing by clicking the button “Report 
> > Phishing” on the Outlook toolbar.
> > 
> > 
> > On Tue, 2021-10-12 at 12:43 +, Monsees, Steven C (US) wrote:
> > > g++: error: unrecognized command line option ‘-std=c++14’
> > 
> > It looks like the gcc version is too old on your host for this to
> > work.
> > 
> > Thanks,
> > 
> > Anuj
> 


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

Re: [yocto] #zeus meta-intel

2021-10-12 Thread Anuj Mittal 
bcb-
> default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
> r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:601:
> undefined reference to `vtable for
> llvm::cl::OptionValue std::char_traits, std::allocator > >'
> /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
> pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
> IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
> `llvm::cl::opt,
> std::allocator >, false,
> llvm::cl::parser std::char_traits, std::allocator > > >::opt llvm::cl::desc>(char const (&) [9], llvm::cl::desc const&)':
> /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
> default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
> r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1407:
> undefined reference to `vtable for
> llvm::cl::opt,
> std::allocator >, false,
> llvm::cl::parser std::char_traits, std::allocator > > >'
> /opt/poky/3.1.3/sysroots/x86_64-pokysdk-linux/usr/lib/gcc/x86_64-
> pokysdk-linux/9.3.0/../../../../x86_64-pokysdk-linux/bin/ld:
> IGC/ElfPackager/CMakeFiles/elf_packager.dir/main.cpp.o: in function
> `llvm::cl::parser std::char_traits, std::allocator >
> >::parser(llvm::cl::Option&)':
> /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-
> default/tmp/work/x86_64-linux/intel-graphics-compiler-native/1.0.11-
> r0/recipe-sysroot-native/usr/include/llvm/Support/CommandLine.h:1072:
> undefined reference to `vtable for
> llvm::cl::parser std::char_traits, std::allocator > >'
> collect2: error: ld returned 1 exit status
> 
> -Original Message-
> From: yocto@lists.yoctoproject.org  On
> Behalf Of Anuj Mittal
> Sent: Tuesday, October 12, 2021 10:43 AM
> To: Monsees, Steven C (US) ;
> yocto@lists.yoctoproject.org
> Subject: Re: [yocto] #zeus meta-intel
> 
> External Email Alert
> 
> This email has been sent from an account outside of the BAE Systems
> network.
> 
> Please treat the email with caution, especially if you are requested to
> click on a link, decrypt/open an attachment, or enable macros.  For
> further information on how to spot phishing, access “Cybersecurity
> OneSpace Page” and report phishing by clicking the button “Report
> Phishing” on the Outlook toolbar.
> 
> 
> On Tue, 2021-10-12 at 12:43 +, Monsees, Steven C (US) wrote:
> > g++: error: unrecognized command line option ‘-std=c++14’
> 
> It looks like the gcc version is too old on your host for this to work.
> 
> Thanks,
> 
> Anuj


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

Re: [yocto] #zeus meta-intel

2021-10-12 Thread Anuj Mittal 
On Tue, 2021-10-12 at 12:43 +, Monsees, Steven C (US) wrote:
> g++: error: unrecognized command line option ‘-std=c++14’

It looks like the gcc version is too old on your host for this to work.

Thanks,

Anuj

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

Re: [yocto] #zeus meta-intel

2021-10-08 Thread Anuj Mittal 
On Fri, 2021-10-08 at 16:10 +, Monsees, Steven C (US) via
lists.yoctoproject.org wrote:
> 
> Sorry for my ignorance, but I am missing your point, what exactly
> does the recipe provide when built, intel-opencl-icd ?, will it pull
> in igc ?

It will pull in igc. There's a separate recipe for igc in meta-intel.
compute-runtime will provide intel-opencl-icd but the package name is
different.

You can try building the recipe.

Thanks,

Anuj

> 
> -Original Message-
> From: Mittal, Anuj  
> Sent: Friday, October 8, 2021 12:01 PM
> To: Monsees, Steven C (US) ;
> yocto@lists.yoctoproject.org
> Subject: Re: [yocto] #zeus meta-intel
> 
> External Email Alert
> 
> This email has been sent from an account outside of the BAE Systems
> network.
> 
> Please treat the email with caution, especially if you are requested
> to click on a link, decrypt/open an attachment, or enable macros. 
> For further information on how to spot phishing, access
> “Cybersecurity OneSpace Page” and report phishing by clicking the
> button “Report Phishing” on the Outlook toolbar.
> 
> 
> Sorry, I didn't understand the question. If you want to know which
> version of OpenCL is supported, please see the README for version
> that you're building. Also see:
> 
> https://github.com/intel/compute-runtime/blob/master/opencl/doc/FAQ.md
> 
> Thanks,
> 
> Anuj
> 
> On Fri, 2021-10-08 at 15:30 +, Monsees, Steven C (US) wrote:
> > 
> > Thank you, just for clarification ...
> > 
> > "Building the Neo driver", does that mean no OpenCL library support
> > ?
> > 
> > -Original Message-
> > From: Mittal, Anuj 
> > Sent: Friday, October 8, 2021 11:07 AM
> > To: Monsees, Steven C (US) ; 
> > yocto@lists.yoctoproject.org
> > Subject: Re: [yocto] #zeus meta-intel
> > 
> > External Email Alert
> > 
> > This email has been sent from an account outside of the BAE Systems
> > network.
> > 
> > Please treat the email with caution, especially if you are
> > requested 
> > to click on a link, decrypt/open an attachment, or enable macros. 
> > For 
> > further information on how to spot phishing, access “Cybersecurity 
> > OneSpace Page” and report phishing by clicking the button “Report 
> > Phishing” on the Outlook toolbar.
> > 
> > 
> > On Thu, 2021-10-07 at 16:20 +, Monsees, Steven C (US) via 
> > lists.yoctoproject.org wrote:
> > >  
> > >  
> > > I am looking at “meta-intel/dynamic-layers/clang-layer/recipes-
> > > opencl/compute-runtime”
> > > I have been “told” that this compute-runtime recipe should
> > > basically 
> > > build opencl (Neo) with all the required dependencies… I did not 
> > > think Yocto had support for OpenCL, and was looking to build Neo 
> > > under the SDK.
> > >  
> > > (1)   Is this true, does meta-intell under zeus now support
> > > building 
> > > OpenCL and the OpenCL Graphics compiler under Yocto ?
> > 
> > compute-runtime recipe would allow you to build NEO driver. zeus is
> > no 
> > longer maintained so the version there is old and not tested now
> > but 
> > it should still build.
> > 
> > > (2)   Of so, what would be the proper way to pull this into my
> > > yocto 
> > > build ?
> > 
> > Including meta-intel and meta-clang in bblayers should be enough.
> > 
> > Thanks,
> > 
> > Anuj
> 
> 
> 
> 


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

Re: [yocto] #zeus meta-intel

2021-10-08 Thread Anuj Mittal 
Sorry, I didn't understand the question. If you want to know which
version of OpenCL is supported, please see the README for version that
you're building. Also see:

https://github.com/intel/compute-runtime/blob/master/opencl/doc/FAQ.md

Thanks,

Anuj

On Fri, 2021-10-08 at 15:30 +, Monsees, Steven C (US) wrote:
> 
> Thank you, just for clarification ...
> 
> "Building the Neo driver", does that mean no OpenCL library support ?
> 
> -Original Message-
> From: Mittal, Anuj  
> Sent: Friday, October 8, 2021 11:07 AM
> To: Monsees, Steven C (US) ;
> yocto@lists.yoctoproject.org
> Subject: Re: [yocto] #zeus meta-intel
> 
> External Email Alert
> 
> This email has been sent from an account outside of the BAE Systems
> network.
> 
> Please treat the email with caution, especially if you are requested to
> click on a link, decrypt/open an attachment, or enable macros.  For
> further information on how to spot phishing, access “Cybersecurity
> OneSpace Page” and report phishing by clicking the button “Report
> Phishing” on the Outlook toolbar.
> 
> 
> On Thu, 2021-10-07 at 16:20 +, Monsees, Steven C (US) via
> lists.yoctoproject.org wrote:
> >  
> >  
> > I am looking at “meta-intel/dynamic-layers/clang-layer/recipes-
> > opencl/compute-runtime”
> > I have been “told” that this compute-runtime recipe should basically 
> > build opencl (Neo) with all the required dependencies… I did not
> > think 
> > Yocto had support for OpenCL, and was looking to build Neo under the 
> > SDK.
> >  
> > (1)   Is this true, does meta-intell under zeus now support building 
> > OpenCL and the OpenCL Graphics compiler under Yocto ?
> 
> compute-runtime recipe would allow you to build NEO driver. zeus is no
> longer maintained so the version there is old and not tested now but it
> should still build.
> 
> > (2)   Of so, what would be the proper way to pull this into my yocto 
> > build ?
> 
> Including meta-intel and meta-clang in bblayers should be enough.
> 
> Thanks,
> 
> Anuj


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

Re: [yocto] #zeus meta-intel

2021-10-08 Thread Anuj Mittal 
On Thu, 2021-10-07 at 16:20 +, Monsees, Steven C (US) via
lists.yoctoproject.org wrote:
>  
>  
> I am looking at “meta-intel/dynamic-layers/clang-layer/recipes-
> opencl/compute-runtime”
> I have been “told” that this compute-runtime recipe should basically
> build opencl (Neo) with all the required dependencies…
> I did not think Yocto had support for OpenCL, and was looking to
> build Neo under the SDK.
>  
> (1)   Is this true, does meta-intell under zeus now support building
> OpenCL and the OpenCL Graphics compiler under Yocto ?

compute-runtime recipe would allow you to build NEO driver. zeus is no
longer maintained so the version there is old and not tested now but it
should still build.

> (2)   Of so, what would be the proper way to pull this into my yocto
> build ?

Including meta-intel and meta-clang in bblayers should be enough.

Thanks,

Anuj

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

Re: [yocto] [hardknott][meta-yocto][PATCH 1/4] poky: Use SDKPATHINSTALL instead of SDKPATH

2021-09-26 Thread Anuj Mittal 
Hi Richard,

Can you please merge this series for meta-yocto hardknott?

Thanks,

Anuj

On Tue, 2021-09-21 at 16:27 +0800, Anuj Mittal wrote:
> From: Richard Purdie 
> 
> SDKPATHINSTALL is the default installation path used for the SDK but
> is not
> the path encoded into every SDK binary as the default path. This
> change
> allows it to contain things like dates without requiring every
> nativesdk
> recipe to rebuild.
> 
> Partially fixes [YOCTO #14100]
> 
> Signed-off-by: Richard Purdie 
> (cherry picked from commit a62175ee581bd05661717f0fb89dad2a297b4034)
> Signed-off-by: Anuj Mittal 
> ---
>  meta-poky/conf/distro/poky.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta-poky/conf/distro/poky.conf b/meta-
> poky/conf/distro/poky.conf
> index 1dfce76..d368561 100644
> --- a/meta-poky/conf/distro/poky.conf
> +++ b/meta-poky/conf/distro/poky.conf
> @@ -23,7 +23,7 @@ PREFERRED_VERSION_linux-yocto ?= "5.10%"
>  PREFERRED_VERSION_linux-yocto-rt ?= "5.10%"
>  
>  SDK_NAME = "${DISTRO}-${TCLIBC}-${SDKMACHINE}-${IMAGE_BASENAME}-
> ${TUNE_PKGARCH}-${MACHINE}"
> -SDKPATH = "/opt/${DISTRO}/${SDK_VERSION}"
> +SDKPATHINSTALL = "/opt/${DISTRO}/${SDK_VERSION}"
>  
>  DISTRO_EXTRA_RDEPENDS += "${POKY_DEFAULT_EXTRA_RDEPENDS}"
>  DISTRO_EXTRA_RRECOMMENDS += "${POKY_DEFAULT_EXTRA_RRECOMMENDS}"
> 
> 
> 


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

[yocto] [hardknott][meta-yocto][PATCH 4/4] yocto-bsp/5.10: update to v5.10.63

2021-09-21 Thread Anuj Mittal 
From: Bruce Ashfield 

Updating the reference platforms to match the latest 5.10 -stable in
oe-core.

Signed-off-by: Bruce Ashfield 
Signed-off-by: Richard Purdie 
(cherry picked from commit 77b8e31f706cb29d1efb19305470d9b525fc5a67)
Signed-off-by: Anuj Mittal 
---
 .../linux/linux-yocto_5.10.bbappend  | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.10.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.10.bbappend
index 0e5e3b1..347a411 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.10.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.10.bbappend
@@ -7,17 +7,17 @@ KMACHINE_genericx86 ?= "common-pc"
 KMACHINE_genericx86-64 ?= "common-pc-64"
 KMACHINE_beaglebone-yocto ?= "beaglebone"
 
-SRCREV_machine_genericx86 ?= "c274623910704eefcc98380a17649889ac7e9408"
-SRCREV_machine_genericx86-64 ?= "c274623910704eefcc98380a17649889ac7e9408"
-SRCREV_machine_edgerouter ?= "ac089d661362ba857e235c5630242039b150ae26"
-SRCREV_machine_beaglebone-yocto ?= "a6df693a45f5787d4254e0998f52b4465b2a5efe"
+SRCREV_machine_genericx86 ?= "164ed895bc1e94722e80fe6496b176f6bb815cd4"
+SRCREV_machine_genericx86-64 ?= "164ed895bc1e94722e80fe6496b176f6bb815cd4"
+SRCREV_machine_edgerouter ?= "4ab94e777d8b41ee1ee4c279259e9733bc8049b1"
+SRCREV_machine_beaglebone-yocto ?= "941cc9c3849f96f7eaf109b1e35e05ba366aca56"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
 COMPATIBLE_MACHINE_edgerouter = "edgerouter"
 COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
 
-LINUX_VERSION_genericx86 = "5.10.55"
-LINUX_VERSION_genericx86-64 = "5.10.55"
-LINUX_VERSION_edgerouter = "5.10.55"
-LINUX_VERSION_beaglebone-yocto = "5.10.55"
+LINUX_VERSION_genericx86 = "5.10.63"
+LINUX_VERSION_genericx86-64 = "5.10.63"
+LINUX_VERSION_edgerouter = "5.10.63"
+LINUX_VERSION_beaglebone-yocto = "5.10.63"
-- 
2.31.1


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

[yocto] [hardknott][meta-yocto][PATCH 2/4] local.conf.sample: Update sstate mirror entry with new hash equivalence setting

2021-09-21 Thread Anuj Mittal 
From: Richard Purdie 

Signed-off-by: Richard Purdie 
(cherry picked from commit 1d98182eb9fa059444c935967d1dc075535289db)
Signed-off-by: Anuj Mittal 
---
 meta-poky/conf/local.conf.sample | 6 --
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/meta-poky/conf/local.conf.sample b/meta-poky/conf/local.conf.sample
index a94b613..67124d4 100644
--- a/meta-poky/conf/local.conf.sample
+++ b/meta-poky/conf/local.conf.sample
@@ -225,13 +225,15 @@ BB_DISKMON_DIRS ??= "\
 # Yocto Project SState Mirror
 #
 # The Yocto Project has prebuilt artefacts available for its releases, you can 
enable
-# use of these by uncommenting the following line. This will mean the build 
uses
+# use of these by uncommenting the following lines. This will mean the build 
uses
 # the network to check for artefacts at the start of builds, which does slow 
it down
 # equally, it will also speed up the builds by not having to build things if 
they are
 # present in the cache. It assumes you can download something faster than you 
can build it
 # which will depend on your network.
+# Note: For this to work you also need hash-equivalence passthrough to the 
matching server
 #
-#SSTATE_MIRRORS ?= "file://.* 
http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH";
+#BB_HASHSERVE_UPSTREAM = "typhoon.yocto.io:8687"
+#SSTATE_MIRRORS ?= "file://.* 
http://sstate.yoctoproject.org/3.4/PATH;downloadfilename=PATH";
 
 #
 # Qemu configuration
-- 
2.31.1


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

[yocto] [hardknott][meta-yocto][PATCH 3/4] meta-yocto-bsp: Bump to the v5.10.55

2021-09-21 Thread Anuj Mittal 
From: Kevin Hao 

Build and boot test for all the boards.

Signed-off-by: Kevin Hao 
Signed-off-by: Richard Purdie 
(cherry picked from commit 8b5c126510dbf265dc494ff7c8decbae63f5b597)
Signed-off-by: Anuj Mittal 
---
 .../linux/linux-yocto_5.10.bbappend  | 16 
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.10.bbappend 
b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.10.bbappend
index f8362b6..0e5e3b1 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.10.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.10.bbappend
@@ -7,17 +7,17 @@ KMACHINE_genericx86 ?= "common-pc"
 KMACHINE_genericx86-64 ?= "common-pc-64"
 KMACHINE_beaglebone-yocto ?= "beaglebone"
 
-SRCREV_machine_genericx86 ?= "ab49d2db98bdee2c8c6e17fb59ded9e5292b0f41"
-SRCREV_machine_genericx86-64 ?= "ab49d2db98bdee2c8c6e17fb59ded9e5292b0f41"
-SRCREV_machine_edgerouter ?= "274d63799465eebfd201b3e8251f16d29e93a978"
-SRCREV_machine_beaglebone-yocto ?= "ab49d2db98bdee2c8c6e17fb59ded9e5292b0f41"
+SRCREV_machine_genericx86 ?= "c274623910704eefcc98380a17649889ac7e9408"
+SRCREV_machine_genericx86-64 ?= "c274623910704eefcc98380a17649889ac7e9408"
+SRCREV_machine_edgerouter ?= "ac089d661362ba857e235c5630242039b150ae26"
+SRCREV_machine_beaglebone-yocto ?= "a6df693a45f5787d4254e0998f52b4465b2a5efe"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
 COMPATIBLE_MACHINE_edgerouter = "edgerouter"
 COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
 
-LINUX_VERSION_genericx86 = "5.10.43"
-LINUX_VERSION_genericx86-64 = "5.10.43"
-LINUX_VERSION_edgerouter = "5.10.43"
-LINUX_VERSION_beaglebone-yocto = "5.10.43"
+LINUX_VERSION_genericx86 = "5.10.55"
+LINUX_VERSION_genericx86-64 = "5.10.55"
+LINUX_VERSION_edgerouter = "5.10.55"
+LINUX_VERSION_beaglebone-yocto = "5.10.55"
-- 
2.31.1


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

[yocto] [hardknott][meta-yocto][PATCH 1/4] poky: Use SDKPATHINSTALL instead of SDKPATH

2021-09-21 Thread Anuj Mittal 
From: Richard Purdie 

SDKPATHINSTALL is the default installation path used for the SDK but is not
the path encoded into every SDK binary as the default path. This change
allows it to contain things like dates without requiring every nativesdk
recipe to rebuild.

Partially fixes [YOCTO #14100]

Signed-off-by: Richard Purdie 
(cherry picked from commit a62175ee581bd05661717f0fb89dad2a297b4034)
Signed-off-by: Anuj Mittal 
---
 meta-poky/conf/distro/poky.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-poky/conf/distro/poky.conf b/meta-poky/conf/distro/poky.conf
index 1dfce76..d368561 100644
--- a/meta-poky/conf/distro/poky.conf
+++ b/meta-poky/conf/distro/poky.conf
@@ -23,7 +23,7 @@ PREFERRED_VERSION_linux-yocto ?= "5.10%"
 PREFERRED_VERSION_linux-yocto-rt ?= "5.10%"
 
 SDK_NAME = 
"${DISTRO}-${TCLIBC}-${SDKMACHINE}-${IMAGE_BASENAME}-${TUNE_PKGARCH}-${MACHINE}"
-SDKPATH = "/opt/${DISTRO}/${SDK_VERSION}"
+SDKPATHINSTALL = "/opt/${DISTRO}/${SDK_VERSION}"
 
 DISTRO_EXTRA_RDEPENDS += "${POKY_DEFAULT_EXTRA_RDEPENDS}"
 DISTRO_EXTRA_RRECOMMENDS += "${POKY_DEFAULT_EXTRA_RRECOMMENDS}"
-- 
2.31.1


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

[yocto] [hardknott][yocto-autobuilder-helper][PATCH 1/2] config.json: Add BB_HASHSERVE to SDK_LOCAL_CONF_BLACKLIST

2021-09-21 Thread Anuj Mittal 
From: Richard Purdie 

This should avoid issues with the hashequiv code attempting to contact
an non-existent server in the eSDKs built by the project.

[YOCTO #14471]

Signed-off-by: Richard Purdie 
(cherry picked from commit 4db17f4c9da4efb48d428256efb696d86935a3ea)
Signed-off-by: Anuj Mittal 
---
 config.json | 1 +
 1 file changed, 1 insertion(+)

diff --git a/config.json b/config.json
index 0ee7572..622908b 100644
--- a/config.json
+++ b/config.json
@@ -55,6 +55,7 @@
 "SANITY_TESTED_DISTROS = ''",
 "SDK_EXT_TYPE = 'minimal'",
 "SDK_INCLUDE_TOOLCHAIN = '1'",
+"SDK_LOCAL_CONF_BLACKLIST:append = 'BB_HASHSERVE'",
 "BB_DISKMON_DIRS = 'STOPTASKS,${TMPDIR},1G,100K 
STOPTASKS,${DL_DIR},1G STOPTASKS,${SSTATE_DIR},1G STOPTASKS,/tmp,100M,100K 
ABORT,${TMPDIR},100M,1K ABORT,${DL_DIR},100M ABORT,${SSTATE_DIR},100M 
ABORT,/tmp,10M,1K'",
 "BB_HASHSERVE = 'typhoon.yocto.io:8686'",
 "RUNQEMU_TMPFS_DIR = '/home/pokybuild/tmp'"
-- 
2.31.1


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

[yocto] [hardknott][yocto-autobuilder-helper][PATCH 2/2] config.json: Ensure BB_HASHSERVE is set in SDKs to auto

2021-09-21 Thread Anuj Mittal 
From: Richard Purdie 

Signed-off-by: Richard Purdie 
(cherry picked from commit 4689763b513521fc70cca576b88035de240a3ba6)
Signed-off-by: Anuj Mittal 
---
 config.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config.json b/config.json
index 622908b..33d36ad 100644
--- a/config.json
+++ b/config.json
@@ -31,7 +31,7 @@
 "DLDIR" : "DL_DIR = '${BASE_SHAREDDIR}/current_sources'",
 "SSTATEDIR" : ["SSTATE_DIR ?= '${BASE_SHAREDDIR}/pub/sstate'"],
 "SSTATEDIR_RELEASE" : ["SSTATE_MIRRORS += 'file://.* 
file://${BASE_SHAREDDIR}/pub/sstate/PATH'", "SSTATE_DIR ?= 
'${BASE_PUBLISHDIR}/sstate/@RELEASENUM@'"],
-"SDKEXTRAS" : ["SSTATE_MIRRORS += '\\", "file://.* 
http://sstate.yoctoproject.org/dev/@RELEASENUM@PATH;downloadfilename=PATH'"],
+"SDKEXTRAS" : ["SSTATE_MIRRORS += '\\", "file://.* 
http://sstate.yoctoproject.org/dev/@RELEASENUM@PATH;downloadfilename=PATH'", 
"BB_HASHSERVE = 'auto'"],
 "BUILDINFO" : false,
 "BUILDHISTORY" : false,
 "BUILDINFOVARS" : ["INHERIT += 'image-buildinfo'", 
"IMAGE_BUILDINFO_VARS_append = ' IMAGE_BASENAME IMAGE_NAME'"],
-- 
2.31.1


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

Re: [yocto] Dependencies are not resolved correctly when building the SDK

2021-08-26 Thread Anuj Mittal 
On Thu, 2021-08-26 at 00:44 -0700, asconcepcion wrote:
> Hi Anuj,
> 
> Thanks for the tip. I added "BBCLASSEXTEND += "nativesdk"" to the
> recipe of the dependency package, but I still get the same error. Do
> you know if I could be missing something else?
> 

Please post the exact error that you're getting. 

Thanks,

Anuj

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

Re: [yocto] Dependencies are not resolved correctly when building the SDK

2021-08-26 Thread Anuj Mittal 
On Wed, 2021-08-25 at 23:54 -0700, asconcepcion wrote:
> Hello,
> 
> We have a custom package recipe that has a build dependency with
> another one (defined in yocto with the DEPENDS variable). If we build
> an image that includes that package, bitbake will build the
> dependency
> before building the package, as expected. However, if we build the
> SDK
> associated to that image (with bitbake  -c populate_sdk), it
> will fail in building that package because of a missing dependency.
> Does anyone know what could be causing this behavior?

Can that recipe for dependency package actually be built for nativesdk?

Thanks,

Anuj

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

Re: [yocto] Hardknott: grub immediately reboots

2021-04-28 Thread Anuj Mittal 


> -Original Message-
> From: yocto@lists.yoctoproject.org  On Behalf Of
> Tony Battersby
> Sent: Tuesday, April 27, 2021 03:07 AM
> To: yocto@lists.yoctoproject.org
> Subject: [yocto] Hardknott: grub immediately reboots
> 
> After upgrading from Dunfell (YP 3.1) to Hardknott (YP 3.3), our firmware was
> unable to boot.  Our target hardware is x86-64 booting in legacy BIOS mode 
> using
> grub on a variety of motherboards and CPUs.  The grub menu would never show 
> up;
> instead it would reboot immediately, leading to an endless reboot loop.
> 
> I have two different workarounds.  Create a bbappend file for grub, and do 
> one of the
> following two things:
> 
> 1) Add the following line:
> 
> CFLAGS_remove = "-O2"

I think we should probably remove this. That's what Fedora also seems to be 
doing so Os is used.

https://src.fedoraproject.org/rpms/grub2/blob/rawhide/f/grub.macros#_19

and what grub configure expects:

https://git.savannah.gnu.org/cgit/grub.git/tree/configure.ac#n41

Thanks,

Anuj

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

Re: [yocto] #yocto opencl

2021-04-28 Thread Anuj Mittal 
> -Original Message-
> From: yocto@lists.yoctoproject.org  On Behalf Of
> Khem Raj
> Sent: Thursday, April 29, 2021 10:07 AM
> To: steven.mons...@baesystems.com; yocto@lists.yoctoproject.org
> Subject: Re: [yocto] #yocto opencl
> 
> 
> 
> On 4/28/21 10:30 AM, Monsees, Steven C (US) via lists.yoctoproject.org
> wrote:
> > Can someone tell me is this supported under Yocto in any way?
> >
> > meta-beignet/recipes-opencl at ross * rossburton/meta-beignet * GitHub
> > 
> >
> > Any docs, or updates ?
> >
> > Wanted to know if this would work under Zeus, with meta-clang ?
> >
> > Looking to build opencl shared library support...
> 
> meta-intel has it see
> https://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/dynamic-layers/clang-
> layer/recipes-opencl/opencl-clang?h=zeus
> 

Yes, please see the compute-runtime recipe that builds NEO driver instead for 
later platforms. More details on the project site:

https://github.com/intel/compute-runtime/blob/master/opencl/doc/FAQ.md

Thanks,

Anuj

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

[yocto] [yocto-autobuilder2][PATCH] schedulers.py: build docs for hardknott/1.50 as well

2021-04-21 Thread Anuj Mittal 
Signed-off-by: Anuj Mittal 
---
 schedulers.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/schedulers.py b/schedulers.py
index 920daab..9d81806 100644
--- a/schedulers.py
+++ b/schedulers.py
@@ -364,7 +364,7 @@ schedulers.append(sched.Nightly(name='nightly-auh', 
branch='master', properties=
 
 # If any of our sphinx docs branches change, trigger a build
 schedulers.append(sched.AnyBranchScheduler(name="yocto-docs-changed",
-change_filter=util.ChangeFilter(project=["yocto-docs"], 
branch=["master", "master-next", "gatesgarth", "dunfell", "transition"]),
+change_filter=util.ChangeFilter(project=["yocto-docs"], 
branch=["master", "master-next", "hardknott", "gatesgarth", "dunfell", 
"transition"]),
 codebases = ['', 'yocto-docs', 'bitbake'],
 treeStableTimer=60,
 builderNames=["docs"]))
@@ -376,7 +376,7 @@ def isbitbakeDocFile(change):
 return True
 return False
 schedulers.append(sched.AnyBranchScheduler(name="bitbake-docs-changed",
-change_filter=util.ChangeFilter(project=["bitbake"], 
branch=["master", "1.48", "1.46"]),
+change_filter=util.ChangeFilter(project=["bitbake"], 
branch=["master", "1.50", "1.48", "1.46"]),
 codebases = ['', 'yocto-docs', 'bitbake'],
 fileIsImportant=isbitbakeDocFile,
 onlyImportant=True,
-- 
2.30.2


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

[yocto] [yocto-autobuilder2][PATCH] schedulers.py: add hardknott to release selector

2021-04-21 Thread Anuj Mittal 
Keep meta-arm at master since there's no hardknott there yet.

Signed-off-by: Anuj Mittal 
---
 schedulers.py | 12 +++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/schedulers.py b/schedulers.py
index 8479290..920daab 100644
--- a/schedulers.py
+++ b/schedulers.py
@@ -169,7 +169,7 @@ def parent_scheduler(target):
 name="branchselector",
 default="master",
 label="Release Shortcut Selector",
-choices=["master", "master-next", "mut", "gatesgarth", "dunfell", 
"zeus", "warrior", "thud", "sumo", "rocko", "pyro", "morty"],
+choices=["master", "master-next", "mut", "hardknott", 
"gatesgarth", "dunfell", "zeus", "warrior", "thud", "sumo", "rocko", "pyro", 
"morty"],
 selectors={
   'master': {
 'branch': 'master',
@@ -202,6 +202,16 @@ def parent_scheduler(target):
 'branch_meta-mingw': 'master',
 'branch_oecore': 'master',
   },
+  'hardknott': {
+'branch': 'hardknott',
+'branch_poky': 'hardknott',
+'branch_bitbake': '1.50',
+'branch_meta-arm': 'master',
+'branch_meta-gplv2': 'hardknott',
+'branch_meta-intel': 'hardknott',
+'branch_meta-mingw': 'hardknott',
+'branch_oecore': 'hardknott',
+  },
   'gatesgarth': {
 'branch': 'gatesgarth',
 'branch_poky': 'gatesgarth',
-- 
2.30.2


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

[yocto] [yocto-autobuilder-helper][PATCH] config.json: add hardknott for buildhistory

2021-04-21 Thread Anuj Mittal 
Signed-off-by: Anuj Mittal 
---
 config.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config.json b/config.json
index 5bfa240..3beb990 100644
--- a/config.json
+++ b/config.json
@@ -5,7 +5,7 @@
 
 "BUILD_HISTORY_DIR" : "buildhistory",
 "BUILD_HISTORY_REPO" : 
"ssh://g...@push.yoctoproject.org/poky-buildhistory",
-"BUILD_HISTORY_DIRECTPUSH" : ["poky:morty", "poky:pyro", "poky:rocko", 
"poky:sumo", "poky:thud", "poky:warrior", "poky:zeus", "poky:dunfell", 
"poky:gatesgarth", "poky:master"],
+"BUILD_HISTORY_DIRECTPUSH" : ["poky:morty", "poky:pyro", "poky:rocko", 
"poky:sumo", "poky:thud", "poky:warrior", "poky:zeus", "poky:dunfell", 
"poky:gatesgarth", "poky:hardknott", "poky:master"],
 "BUILD_HISTORY_FORKPUSH" : {"poky-contrib:ross/mut" : "poky:master", 
"poky:master-next" : "poky:master"},
 
 "BUILDTOOLS_URL_TEMPLOCAL" : 
"/srv/autobuilder/autobuilder.yoctoproject.org/pub/non-release/20200309-15/buildtools/x86_64-buildtools-extended-nativesdk-standalone-3.0+snapshot-20200309.sh",
-- 
2.30.2


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

Re: [yocto] Trouble booting basic x86 image

2021-02-23 Thread Anuj Mittal 
On Tue, 2021-02-23 at 01:01 -0800, Paul D. DeRocco wrote:
> Yocto Gatesgarth, using meta-intel to build core-image-minimal
> Intel D2700MUD mini-ITX mobo with D2700 Atom
> Ordinary USB 2.0 flash drive
> 
> I followed the instructions in the meta-intel README, and had no
> problems
> building the intel-core2-32 and intel-corei7-64 machines, as well as
> the
> latter with an x32 tune. But whenever I try to boot any of them, I
> get the
> following stuff from the kernel:
> 
> usb 1-6: new high-speed USB device number 4 using ehci-pci
> usb-storage 1-6:1.0: USB Mass Storage device detected
> usb-storage 1-6:1.0:  Quirks match for vid 090c pid 1000: 400
> scsi host4: usb-storage 1-6:1.0
> scsi 4:0:0:0: Direct-Access FLASH    Drive SM_USB20   1100 PQ: 0
> ANSI: 4
> sd 4:0:0:0: Attached scsi generic sg0 type 0
> sd 4:0:0:0: [sda] 3932160 512-byte logical blocks: (2.01 GB/1.88 GiB)
> sd 4:0:0:0: [sda] Write Protect is off
> sd 4:0:0:0: [sda] No Caching mode page found
> sd 4:0:0:0: [sda] Assume drive cache: write through
>  sda:
> sd 4:0:0:0: [sda] Attached SCSI removable disk
> (countdown from 27 to 0)
> Mounted filesystems
> Available block devices
> major minor  #blocks  name
>    1    0   4096 ram0
>     ... (others edited out)
>    1   15   4096 ram15
>    8    0    1966080 sda
> Cannot find rootfs.img file in /run/media/* , dropping to a shell

It looks like you are using the live option in hddimg image? Can you
try adding "rootwait" to kernel parameters and see if that works?

Not sure why it's not dropping to shell, but may be try adding explicit
call to /bin/sh in meta/recipes-core/initrdscripts/files/init-live.sh
before this point to make sure the media is actually mounted at that
point.

Also, have you tried wic image to see if that works?

Thanks,

Anuj

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

Re: [yocto] #yocto #kernel "yocto-check-layer"

2021-02-10 Thread Anuj Mittal 
On Wed, 2021-02-10 at 13:55 +, Monsees, Steven C (US) via
lists.yoctoproject.org wrote:
>  
> Mb build was setup and done under one layer, with “distro” and “bsp“
> at the same layer, I wanted to split them up into separate layers
> inorder to better conform to the Yocto standard…. (Note my kernel
> builds and runs correctly when split or not split)
>  
> When not split “Yocto-check-layer” calls me out for having “distro”
> and “bsp” in same layer, when I split them I am seeing the following
> for each new layer:
>  
> Can someone explain the errors the script is reporting and how to
> resolve (these are not seen build the split or non-split images) ?
>  
> 08:43 smonsees@yix490031
> /disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-
> limws/builds/sbcb-default>yocto-check-layer
> /disk0/scratch/smonsees/yocto/workspace_3/poky/../meta-bae/meta-
> limws/meta-intel/meta-intel-bsp
> INFO: Detected layers:
> INFO: meta-intel-bsp: LayerType.BSP,
> /disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/meta-
> intel/meta-intel-bsp
> INFO: 
> INFO: Setting up for meta-intel-bsp(LayerType.BSP),
> /disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/meta-
> intel/meta-intel-bsp
> INFO: Getting initial bitbake variables ...
> INFO: Getting initial signatures ...
> INFO: Generating signatures failed. This might be due to some parse
> error and/or general layer incompatibilities.
> Command: BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE BB_SIGNATURE_HANDLER"
> BB_SIGNATURE_HANDLER="OEBasicHash" bitbake -S none world
> Output:
> Parsing recipes...done.
> Parsing of 2450 .bb files complete (0 cached, 2450 parsed). 3645
> targets, 91 skipped, 0 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
> ERROR: Nothing RPROVIDES 'shim' (but
> /disk0/scratch/smonsees/yocto/workspace_3/poky/meta/recipes-
> core/packagegroups/packagegroup-base.bb RDEPENDS on or otherwise
> requires it)
> NOTE: Runtime target 'shim' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['shim']
> ERROR: Required build target 'meta-world-pkgdata' has no buildable
> providers.
> Missing or unbuildable dependency chain was: ['meta-world-pkgdata',
> 'packagegroup-base', 'shim']

It looks like this packagegroup has a RDEPENDS on "shim" while the code
can't find the recipe. If that RDEPENDS is correct, this layer probably
needs to add a LAYERDEPENDS on a layer that has this recipe in
layer.conf.


Thanks,

Anuj

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

Re: [yocto] Image installation problems after an upgrade to gatesgarth

2021-02-09 Thread Anuj Mittal 
On Tue, 2021-02-09 at 08:25 -0700, Ori Pessach wrote:
> Hi,
> 
> I have an image that was building and working fine with an older
> release of Poky. The target system is genericx86-64, and I'm trying
> to create a boot USB drive that installs the system on the PC it
> boots on. 
> 
> Like I said, this was working fine before.
> 
> With gatesgarth, I'm only getting the "boot" option in grub. I have a
> grub-bootconf bbappend file that sets LABELS to "install" (the only
> option I want) and a couple of bbappend files modifying the init-
> install-efi.sh file in initrdscripts. I can see that the grub.cfg
> file generated during the build is correct (under
> tmp/work/genericx86_64-poky-linux/grub-bootconf/1.00-
> r0/image/boot/EFI/BOOT/grub.cfg) and yet, the wic image only has the
> boot option.
> 
> How do I get the install grub option into the image?

You can build the hddimg image by changing IMAGE_FSTYPES to live which
has the boot and install option. I think it used to be live until zeus.

If you want to use that init-install-efi script with wic, these steps
might help:

https://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/README#n208


Thanks,

Anuj

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

Re: [yocto] How to select Linux kernel version?

2021-01-05 Thread Anuj Mittal 
On Wed, 2021-01-06 at 17:02 +1100, JH wrote:
> Hi,
> 
> I replaced Linux kernel version from 4.19 by 5.10 bb file, but it
> still built 4.19 zImage, I add PREFERRED_VERSION_linux-yocto =
> "5.10%"
> in local.conf, it still built 4.19 zImage. Where the linux kernel
> version is defined in configure files?
> 

Is the PREFERRED_PROVIDER_virtual/kernel set to linux-yocto? You need
to set the PREFERRED_VERSION for kernel that you are using ... 

bitbake -e virtual/kernel output should help see how it's being set and
where.

Thanks,

Anuj

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

Re: [yocto] [ANNOUNCEMENT] Yocto Project 3.2.1 (gatesgarth-24.0.1) is Released

2020-12-22 Thread Anuj Mittal 
On Tue, 2020-12-15 at 23:07 +, Peter Kjellerstedt wrote:
> > Repository Name: meta-gplv2
> > Repository Location: https://git.yoctoproject.org/git/meta-gplv2
> > Branch: gatesgarth
> > Tag: yocto-3.2.1
> 
> The yocto-3.2.1 and gatesgarth-24.0.1 tags for meta-gplv2 have been
> incorrectly 
> set on the dunfell branch rather than the gatesgarth branch. The Git
> revision 
> and tar balls below are correct though. Since the tags are signed I
> do now want 
> to modify them myself, so please correct them as soon as possible.

Vineela isn't working this week I think so she might not be able to
help but it looks like the commit tagged is on gatesgarth ...

https://git.yoctoproject.org/clean/cgit.cgi/meta-gplv2/log/?h=gatesgarth

$ git branch -a --contains yocto-3.2.1
* master
  remotes/origin/HEAD -> origin/master
  remotes/origin/gatesgarth
  remotes/origin/master
  remotes/origin/master-next

Thanks,

Anuj

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

Re: [yocto] [yocto-autobuilder2 PATCH] config.json: drop redundant meta-kernel mentions

2020-11-19 Thread Anuj Mittal 
Hi Ross

On Mon, 2020-11-16 at 14:59 +, Ross Burton wrote:
> From: Ross Burton 
> 

For gatesgarth, this is causing:

FileNotFoundError: [Errno 2] No such file or directory:
'/home/pokybuild/yocto-worker/meta-arm/build/repos/meta-kernel'

https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/472

meta-arm gatesgarth needs meta-kernel?

Thanks,

Anuj

> Signed-off-by: Ross Burton 
> ---
>  config.json | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/config.json b/config.json
> index 11a2664..c57260a 100644
> --- a/config.json
> +++ b/config.json
> @@ -275,9 +275,8 @@
>  "TEMPLATE" : "ltp-qemu"
>  },
>  "meta-arm" : {
> -    "NEEDREPOS" : ["poky", "meta-arm", "meta-kernel"],
> +    "NEEDREPOS" : ["poky", "meta-arm"],
>  "ADDLAYER" : [
> -    "${BUILDDIR}/../meta-kernel",
>  "${BUILDDIR}/../meta-arm/meta-arm-toolchain",
>  "${BUILDDIR}/../meta-arm/meta-arm",
>  "${BUILDDIR}/../meta-arm/meta-arm-bsp"
> 
> 
> 





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

Re: [yocto] [yocto-autobuilder2 PATCH] config.json: drop redundant meta-kernel mentions

2020-11-19 Thread Anuj Mittal 
Hi Ross

On Mon, 2020-11-16 at 14:59 +, Ross Burton wrote:
> From: Ross Burton 
> 

For gatesgarth, this is causing:

FileNotFoundError: [Errno 2] No such file or directory:
'/home/pokybuild/yocto-worker/meta-arm/build/repos/meta-kernel'

https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/472

meta-arm gatesgarth needs meta-kernel?

Thanks,

Anuj

> Signed-off-by: Ross Burton 
> ---
>  config.json | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/config.json b/config.json
> index 11a2664..c57260a 100644
> --- a/config.json
> +++ b/config.json
> @@ -275,9 +275,8 @@
>  "TEMPLATE" : "ltp-qemu"
>  },
>  "meta-arm" : {
> -    "NEEDREPOS" : ["poky", "meta-arm", "meta-kernel"],
> +    "NEEDREPOS" : ["poky", "meta-arm"],
>  "ADDLAYER" : [
> -    "${BUILDDIR}/../meta-kernel",
>  "${BUILDDIR}/../meta-arm/meta-arm-toolchain",
>  "${BUILDDIR}/../meta-arm/meta-arm",
>  "${BUILDDIR}/../meta-arm/meta-arm-bsp"
> 
> 
> 





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

Re: [yocto] [yocto-autobuilder2 PATCH] config.json: drop redundant meta-kernel mentions

2020-11-19 Thread Anuj Mittal 
Hi Ross

On Mon, 2020-11-16 at 14:59 +, Ross Burton wrote:
> From: Ross Burton 
> 

For gatesgarth, this is causing:

FileNotFoundError: [Errno 2] No such file or directory:
'/home/pokybuild/yocto-worker/meta-arm/build/repos/meta-kernel'

https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/472

meta-arm gatesgarth needs meta-kernel?

Thanks,

Anuj

> Signed-off-by: Ross Burton 
> ---
>  config.json | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/config.json b/config.json
> index 11a2664..c57260a 100644
> --- a/config.json
> +++ b/config.json
> @@ -275,9 +275,8 @@
>  "TEMPLATE" : "ltp-qemu"
>  },
>  "meta-arm" : {
> -    "NEEDREPOS" : ["poky", "meta-arm", "meta-kernel"],
> +    "NEEDREPOS" : ["poky", "meta-arm"],
>  "ADDLAYER" : [
> -    "${BUILDDIR}/../meta-kernel",
>  "${BUILDDIR}/../meta-arm/meta-arm-toolchain",
>  "${BUILDDIR}/../meta-arm/meta-arm",
>  "${BUILDDIR}/../meta-arm/meta-arm-bsp"
> 
> 
> 





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

Re: [yocto] [yocto-autobuilder2 PATCH] config.json: drop redundant meta-kernel mentions

2020-11-18 Thread Anuj Mittal 
Hi Ross

On Mon, 2020-11-16 at 14:59 +, Ross Burton wrote:
> From: Ross Burton 
> 

For gatesgarth, this is causing:

FileNotFoundError: [Errno 2] No such file or directory:
'/home/pokybuild/yocto-worker/meta-arm/build/repos/meta-kernel'

https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/472

meta-arm gatesgarth needs meta-kernel?

Thanks,

Anuj

> Signed-off-by: Ross Burton 
> ---
>  config.json | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/config.json b/config.json
> index 11a2664..c57260a 100644
> --- a/config.json
> +++ b/config.json
> @@ -275,9 +275,8 @@
>  "TEMPLATE" : "ltp-qemu"
>  },
>  "meta-arm" : {
> -    "NEEDREPOS" : ["poky", "meta-arm", "meta-kernel"],
> +    "NEEDREPOS" : ["poky", "meta-arm"],
>  "ADDLAYER" : [
> -    "${BUILDDIR}/../meta-kernel",
>  "${BUILDDIR}/../meta-arm/meta-arm-toolchain",
>  "${BUILDDIR}/../meta-arm/meta-arm",
>  "${BUILDDIR}/../meta-arm/meta-arm-bsp"
> 
> 
> 


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

Re: [yocto] [PATCH 0/3] yocto-bsp/poky: kernel updates and default

2020-08-23 Thread Anuj Mittal 
Hi Bruce,

On Fri, 2020-08-21 at 15:07 -0400, Bruce Ashfield wrote:
> From: Bruce Ashfield 
> 
> Richard,
> 
> Similar to oe-core, these are the patches I'm carrying to update the
> reference BSPs to the latest 5.4 (we still need a 5.8 bbappend and
> confirmed booting), as well as a switch to 5.8 as the default.
> 
> That being said, I'm not sure of the way you'd like the default
> kernel
> set to differentiate between the reference BSPs and qemu. So
> currently,
> I just have the single preferred version set.
> 

Should we also update PREFERRED_VERSION for linux-yocto-tiny for poky-
tiny DISTRO? It is currently pointing to 5.0 ...

Thanks,

Anuj


> Cheers,
> 
> Bruce
> 
> The following changes since commit
> c9d0bb421a2f7c6783f2c2bbf47c95da5537985d:
> 
>   linux-yocto/5.8: update to v5.8.2 (2020-08-21 14:55:05 -0400)
> 
> are available in the Git repository at:
> 
>   git://git.yoctoproject.org/poky-contrib zedd/kernel-yocto
>   
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-yocto
> 
> Bruce Ashfield (3):
>   poky: set preferred version for linux-yocto to be v5.8
>   yocto-bsp: update to v5.4.56
>   yocto-bsp: update to v5.4.58
> 
>  meta-poky/conf/distro/poky.conf  |  2 +-
>  .../linux/linux-yocto_5.4.bbappend   | 16 
> 
>  2 files changed, 9 insertions(+), 9 deletions(-)
> 
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50326): https://lists.yoctoproject.org/g/yocto/message/50326
Mute This Topic: https://lists.yoctoproject.org/mt/76335682/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-dpdk] is there a plan to support newer dpdk?

2020-07-16 Thread Anuj Mittal 
On Thu, 2020-07-16 at 12:11 -0700, Rick Liu via lists.yoctoproject.org
wrote:
> Hi,
> 
> From meta-dpdk.git, the latest dufell branch is using dpdk 19.11.2.
> Is there a plan to support dpdk 20.0x? 
> (and maybe using meason/ninja to build?)

Not on the dunfell branch. If you already have the recipe, I can add it
to master branch which I think should build fine with oe-core dunfell
too.

Thanks,

Anuj
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49982): https://lists.yoctoproject.org/g/yocto/message/49982
Mute This Topic: https://lists.yoctoproject.org/mt/75548824/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-intel][PATCH] conf:machine: Use weak reference for SERIAL_CONSOLES variable

2020-04-13 Thread Anuj Mittal 
On Tue, 2020-04-14 at 08:25 +0200, Marek Belisko wrote:
> This add possibility to override in custom layer.
> 
> Signed-off-by: Marek Belisko 
> ---
>  conf/machine/intel-core2-32.conf   | 2 +-
>  conf/machine/intel-corei7-64.conf  | 2 +-
>  conf/machine/intel-skylake-64.conf | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/conf/machine/intel-core2-32.conf b/conf/machine/intel-
> core2-32.conf
> index 20c9872..384ad1e 100644
> --- a/conf/machine/intel-core2-32.conf
> +++ b/conf/machine/intel-core2-32.conf
> @@ -27,7 +27,7 @@ XSERVER ?= "${XSERVER_X86_BASE} \
> "
>  
>  SYSLINUX_OPTS = "serial 0 115200"
> -SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS1 115200;ttyPCH0"
> +SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyS1 115200;ttyPCH0"

I think having just this would make this statement not do anything as
these machine files includes x86-base.inc which also sets this variable
using a ?=. 

This would probably also need a ??= in x86-base.inc.

Thanks,

Anuj

>  APPEND += "rootwait console=ttyS0,115200 console=ttyPCH0,115200
> console=tty0"
>  
>  IMAGE_FSTYPES += "wic"
> diff --git a/conf/machine/intel-corei7-64.conf b/conf/machine/intel-
> corei7-64.conf
> index 6164bf3..2009537 100644
> --- a/conf/machine/intel-corei7-64.conf
> +++ b/conf/machine/intel-corei7-64.conf
> @@ -32,7 +32,7 @@ XSERVER ?= "${XSERVER_X86_BASE} \
> "
>  
>  SYSLINUX_OPTS = "serial 0 115200"
> -SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS1 115200;ttyS2"
> +SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyS1 115200;ttyS2"
>  APPEND += "rootwait console=ttyS0,115200 console=tty0"
>  
>  IMAGE_FSTYPES += "wic"
> diff --git a/conf/machine/intel-skylake-64.conf b/conf/machine/intel-
> skylake-64.conf
> index e367951..503a982 100644
> --- a/conf/machine/intel-skylake-64.conf
> +++ b/conf/machine/intel-skylake-64.conf
> @@ -25,7 +25,7 @@ XSERVER ?= "${XSERVER_X86_BASE} \
> "
>  
>  SYSLINUX_OPTS = "serial 0 115200"
> -SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS1 115200;ttyS2"
> +SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyS1 115200;ttyS2"
>  APPEND += "rootwait console=ttyS0,115200 console=tty0"
>  
>  IMAGE_FSTYPES += "wic"
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49133): https://lists.yoctoproject.org/g/yocto/message/49133
Mute This Topic: https://lists.yoctoproject.org/mt/73005096/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] meta-intel: Override SERIAL_CONSOLES variable

2020-04-10 Thread Anuj Mittal 
Could you send a patch please?

Thanks,

Anuj

> -Original Message-
> From: yocto@lists.yoctoproject.org  On Behalf Of
> Leon Woestenberg
> Sent: Saturday, April 11, 2020 04:48 AM
> To: Marek Belisko 
> Cc: yocto 
> Subject: Re: [yocto] meta-intel: Override SERIAL_CONSOLES variable
> 
> Hi all,
> 
> On Fri, Apr 10, 2020 at 8:56 AM Marek Belisko  wrote:
> >
> > Hi,
> >
> > in meta-intel in machine configuration SERIAL_CONSOLES are defined as
> > : SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS1 115200;ttyS2"
> >
> For a more generic solution, could this be made  a weak assignment?
> 
> I am on a SMARC x86-64 module which only one serial is useful, so I would 
> like to
> downtune this variable as well.
> 
> Regards,
> 
> Leon.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49116): https://lists.yoctoproject.org/g/yocto/message/49116
Mute This Topic: https://lists.yoctoproject.org/mt/72915847/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Bitbake error

2020-02-25 Thread Anuj Mittal 



On 21-Feb-20 05:16 PM, Iñigo Vicente Waliño wrote:

Hi,

I'm trying to build yocto project ZEUS for imx8m mini.

I have this configuration EXTRA_IMAGE_FEATURES= “ ssh-server-openssh
tools-sdk tools-debug dbg-pkgs dev-pkgs doc-pkgs package-management
tools-profile” in my build/conf/local.con file.

But it reports error when executing *bitbake core-image-base*.
Host environment: Ubuntu 18.04.3 LTS

Can any one explain how to resolve this?


You are probably trying to use an old kernel that doesn't have python3 
support for perf:


https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/tools/perf/Makefile.config?h=linux-4.19.y&id=66dfdff03d196e51322c6a85c0d8db8bb2bdd655

I guess one way to resolve this would be to disable scripting in perf if 
you don't want it.


Thanks,

Anuj
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48610): https://lists.yoctoproject.org/g/yocto/message/48610
Mute This Topic: https://lists.yoctoproject.org/mt/71447647/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

2020-02-19 Thread Anuj Mittal 
> 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
> > >
> > > === Summary 
> > > No high milestone defects.
> > > one new defects are found in this cycle - oeqa/runtime test
> > > 'test_dnf_exclude' failed (Bugid:13797) openssh ptest failed (BUG
> > > id:13796) bash ptest failed (BUG id:13795)
> > >
> > > === Bugs 
> > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=13797

From the error log, it looks like we are trying to install 7.67 while zeus has 
7.66 so it errors out. I am guessing that curl wasn't built in a clean build 
directory so the correct version of curl is deployed. Can this test be re-run 
please?

> > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=13796

This needs:

https://github.com/openssh/openssh-portable/commit/ff31f15773ee173502eec4d7861ec56f26bba381

> > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=13795

Was because of the bash CVE patch.

> >
> > Thank you for logging the defects.
> >
> > I suspect this in now in the hands of the YP TSC.
> 
> What is the stable maintainer's thoughts on this?
> 
> In particular I'm worried about the bash patch and whether the ptest 
> regression above
> is related to that or not? Any recommendation?

Looks like it's related but I don't think the impact is much. The test is 
failing because the line number that is expected to fail changed (because of 
the lines being added in the test). So we should be okay in my opinion.

Thanks,

Anuj
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48518): https://lists.yoctoproject.org/g/yocto/message/48518
Mute This Topic: https://lists.yoctoproject.org/mt/7139/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [PATCH yocto-autobuilder-helper v2 1/3] config: don't run meta-intel in qemu yet

2020-01-14 Thread Anuj Mittal 
Can this be merged in zeus/warrior too please?

Thanks,

Anuj

On Mon, 2019-12-16 at 17:41 +, Ross Burton wrote:
> meta-intel BSPs are not compatible with the qemu BSPs currently, so
> don't
> attempt to execute testimage.
> 
> Signed-off-by: Ross Burton 
> ---
>  config.json | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/config.json b/config.json
> index 5730f85..79695c2 100644
> --- a/config.json
> +++ b/config.json
> @@ -387,7 +387,7 @@
>  "NEEDREPOS" : ["poky", "meta-intel"],
>  "ADDLAYER" : ["${BUILDDIR}/../meta-intel"],
>  "MACHINE" : "intel-corei7-64",
> -"TEMPLATE" : "arch-hw-qemu"
> +"TEMPLATE" : "arch-hw"
>  },
>  "genericx86-64-alt" : {
>  "MACHINE" : "genericx86-64",
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#47964): https://lists.yoctoproject.org/g/yocto/message/47964
Mute This Topic: https://lists.yoctoproject.org/mt/68732955/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [PATCH][yocto-autobuilder-helper] config.json: point to new mailing list addresses

2019-12-13 Thread Anuj Mittal 
Signed-off-by: Anuj Mittal 
---
 config.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/config.json b/config.json
index 3268fda..5730f85 100644
--- a/config.json
+++ b/config.json
@@ -11,7 +11,7 @@
 "REPO_STASH_DIR" : "${BASE_HOMEDIR}/git/mirror",
 "TRASH_DIR" : "${BASE_HOMEDIR}/git/trash",
 
-"QAMAIL_TO" : "yo...@yoctoproject.org",
+"QAMAIL_TO" : "yocto@lists.yoctoproject.org",
 "QAMAIL_CC" : "ota...@ossystems.com.br, yi.z...@windriver.com, 
apoorv.san...@intel.com, ee.peng.y...@intel.com, aaron.chun.yew.c...@intel.com, 
richard.pur...@linuxfoundation.org, akuster...@gmail.com, 
sjolley.yp...@gmail.com, sangeeta.j...@intel.com",
 "WEBPUBLISH_DIR" : "${BASE_SHAREDDIR}/",
 "WEBPUBLISH_URL" : "https://autobuilder.yocto.io/";,
@@ -142,7 +142,7 @@
 "SSTATEDIR_RELEASE" : ["SSTATE_DIR ?= '${HELPERBUILDDIR}/sstate'"],
 "PACKAGE_CLASSES" : "package_rpm",
 "EXTRAPLAINCMDS" : [
-"${SCRIPTSDIR}/build-perf-test-wrapper -r 
${BUILDPERF_RESULTSDIR} -E yocto-p...@yoctoproject.org -d 
${BUILDPERF_STATEDIR}/downloads -w ${BASE_HOMEDIR}/build-perf-test -p 
${HELPERRESULTSDIR}/${HELPERTARGET} -R ${HELPERREPONAME} -b ${HELPERBRANCHNAME} 
--push g...@push.yoctoproject.org:yocto-buildstats"
+"${SCRIPTSDIR}/build-perf-test-wrapper -r 
${BUILDPERF_RESULTSDIR} -E yocto-p...@lists.yoctoproject.org -d 
${BUILDPERF_STATEDIR}/downloads -w ${BASE_HOMEDIR}/build-perf-test -p 
${HELPERRESULTSDIR}/${HELPERTARGET} -R ${HELPERREPONAME} -b ${HELPERBRANCHNAME} 
--push g...@push.yoctoproject.org:yocto-buildstats"
 ],
 "extravars" : [
 "BB_NUMBER_THREADS = '24'",
-- 
2.21.0

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#47679): https://lists.yoctoproject.org/g/yocto/message/47679
Mute This Topic: https://lists.yoctoproject.org/mt/68606683/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-