[[meta-security][PATCH] dm-verity-img.bbclass: add squashfs images
Add squashfs to images supported by verity.
Signed-off-by: Maciek Borzecki <maciek@...> --- classes/dm-verity-img.bbclass | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/classes/dm-verity-img.bbclass b/classes/dm-verity-img.bbclass index dd447e6..e5946bc 100644 --- a/classes/dm-verity-img.bbclass +++ b/classes/dm-verity-img.bbclass @@ -63,7 +63,12 @@ verity_setup() { veritysetup --data-block-size=${DM_VERITY_IMAGE_DATA_BLOCK_SIZE} --hash-offset=$SIZE format $OUTPUT $OUTPUT | tail -n +2 | process_verity } -VERITY_TYPES = "ext2.verity ext3.verity ext4.verity btrfs.verity erofs.verity erofs-lz4.verity erofs-lz4hc.verity" +VERITY_TYPES = " \ + ext2.verity ext3.verity ext4.verity \ + btrfs.verity \ + erofs.verity erofs-lz4.verity erofs-lz4hc.verity \ + squashfs.verity squashfs-xz.verity squashfs-lzo.verity squashfs-lz4.verity squashfs-zst.verity \ +" IMAGE_TYPES += "${VERITY_TYPES}" CONVERSIONTYPES += "verity" CONVERSION_CMD:verity = "verity_setup ${type}" -- 2.39.1
|
|
Re: [meta-security][PATCH] linux-yocto: drop version from bbappends
Hi, On Wed, Feb 01, 2023 at 08:19:42AM -0500, akuster808 wrote:
On 1/30/23 6:01 AM, Mikko Rapeli wrote:
These bbappends apply to multiple kernel versions so no need to make them version dependent. Fixes recipe parsing when using meta-security master branch on kirkstone. In our custom layer we set layer compatibility for kirkstone and I understand why meta-security upstream would not want to do that:
LAYERSERIES_COMPAT_security-layer += 'kirkstone' LAYERSERIES_COMPAT_parsec-layer += 'kirkstone' LAYERSERIES_COMPAT_tpm-layer += 'kirkstone'
While I work towards supporting also yocto master branch and newer releases than kirkstone, I would appreciate if I would not have to branch off layers over minor details like this. Is this a dup of the one sent earlier?
Yes, I wasn't sure if I was on the mailing list or not and send-emailed another one after I was correctly subscribed. Cheers, -Mikko -armin
Signed-off-by: Mikko Rapeli <mikko.rapeli@...> --- .../linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend} | 0 .../linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend} | 0 2 files changed, 0 insertions(+), 0 deletions(-) rename meta-tpm/recipes-kernel/linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend} (100%) rename recipes-kernel/linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend} (100%)
diff --git a/meta-tpm/recipes-kernel/linux/linux-yocto_6.%.bbappend b/meta-tpm/recipes-kernel/linux/linux-yocto_%.bbappend similarity index 100% rename from meta-tpm/recipes-kernel/linux/linux-yocto_6.%.bbappend rename to meta-tpm/recipes-kernel/linux/linux-yocto_%.bbappend diff --git a/recipes-kernel/linux/linux-yocto_6.%.bbappend b/recipes-kernel/linux/linux-yocto_%.bbappend similarity index 100% rename from recipes-kernel/linux/linux-yocto_6.%.bbappend rename to recipes-kernel/linux/linux-yocto_%.bbappend
|
|
[meta-security][PATCH] dm-verity-img.bbclass: add squashfs images
Add squashfs to images supported by verity.
Signed-off-by: Maciek Borzecki <maciek@...> --- classes/dm-verity-img.bbclass | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/classes/dm-verity-img.bbclass b/classes/dm-verity-img.bbclass index dd447e6..e5946bc 100644 --- a/classes/dm-verity-img.bbclass +++ b/classes/dm-verity-img.bbclass @@ -63,7 +63,12 @@ verity_setup() { veritysetup --data-block-size=${DM_VERITY_IMAGE_DATA_BLOCK_SIZE} --hash-offset=$SIZE format $OUTPUT $OUTPUT | tail -n +2 | process_verity } -VERITY_TYPES = "ext2.verity ext3.verity ext4.verity btrfs.verity erofs.verity erofs-lz4.verity erofs-lz4hc.verity" +VERITY_TYPES = " \ + ext2.verity ext3.verity ext4.verity \ + btrfs.verity \ + erofs.verity erofs-lz4.verity erofs-lz4hc.verity \ + squashfs.verity squashfs-xz.verity squashfs-lzo.verity squashfs-lz4.verity squashfs-zst.verity \ +" IMAGE_TYPES += "${VERITY_TYPES}" CONVERSIONTYPES += "verity" CONVERSION_CMD:verity = "verity_setup ${type}" -- 2.39.1
|
|
Re: [meta-raspberrypi] Is Preempt-rt still supported in master / latest releases?
#raspberrypi
In kirkstone for example, you build preempt-rt variant by adding to local.conf:
LINUX_KERNEL_TYPE = "preempt-rt"
Does this no longer work?
|
|
[kirkstone][meta-tpm][PATCH 3/3] oeqa: meta-tpm shut swtpm down before and after testing

Armin Kuster
fixes: swtpm: Could not open TCP socket: Address already in use
Signed-off-by: Armin Kuster <akuster808@...> (cherry picked from commit b5642c519b90f83ab6ec1507db9b3b36db43c548) Signed-off-by: Armin Kuster <akuster808@...> --- meta-tpm/lib/oeqa/runtime/cases/swtpm.py | 2 ++ meta-tpm/lib/oeqa/runtime/cases/tpm2.py | 2 ++ 2 files changed, 4 insertions(+)
diff --git a/meta-tpm/lib/oeqa/runtime/cases/swtpm.py b/meta-tpm/lib/oeqa/runtime/cases/swtpm.py index df47b35..0be5c59 100644 --- a/meta-tpm/lib/oeqa/runtime/cases/swtpm.py +++ b/meta-tpm/lib/oeqa/runtime/cases/swtpm.py @@ -8,11 +8,13 @@ from oeqa.core.decorator.data import skipIfNotFeature class SwTpmTest(OERuntimeTestCase): @classmethod def setUpClass(cls): + cls.tc.target.run('swtpm_ioctl -s --tcp :2322') cls.tc.target.run('mkdir /tmp/myvtpm2') cls.tc.target.run('chown tss:root /tmp/myvtpm2') @classmethod def tearDownClass(cls): + cls.tc.target.run('swtpm_ioctl -s --tcp :2322') cls.tc.target.run('rm -fr /tmp/myvtpm2') @skipIfNotFeature('tpm2','Test tpm2_swtpm_socket requires tpm2 to be in DISTRO_FEATURES') diff --git a/meta-tpm/lib/oeqa/runtime/cases/tpm2.py b/meta-tpm/lib/oeqa/runtime/cases/tpm2.py index e64d19d..8e90dc9 100644 --- a/meta-tpm/lib/oeqa/runtime/cases/tpm2.py +++ b/meta-tpm/lib/oeqa/runtime/cases/tpm2.py @@ -8,10 +8,12 @@ from oeqa.core.decorator.data import skipIfNotFeature class Tpm2Test(OERuntimeTestCase): @classmethod def setUpClass(cls): + cls.tc.target.run('swtpm_ioctl -s --tcp :2322') cls.tc.target.run('mkdir /tmp/myvtpm2') @classmethod def tearDownClass(cls): + cls.tc.target.run('swtpm_ioctl -s --tcp :2322') cls.tc.target.run('rm -fr /tmp/myvtpm2') def check_endlines(self, results, expected_endlines): -- 2.37.3
|
|
[kirkstone][meta-tpm][PATCH 2/3] oeqa/tpm2: fix and cleanup tests

Armin Kuster
Signed-off-by: Armin Kuster <akuster808@...> (cherry picked from commit 3db9e08300c3d5e3f7b6e4e6cb743a914ed3f00b) Signed-off-by: Armin Kuster <akuster808@...> --- meta-tpm/lib/oeqa/runtime/cases/tpm2.py | 25 ++++++++++++++++--------- 1 file changed, 16 insertions(+), 9 deletions(-)
diff --git a/meta-tpm/lib/oeqa/runtime/cases/tpm2.py b/meta-tpm/lib/oeqa/runtime/cases/tpm2.py index c2c95e7..e64d19d 100644 --- a/meta-tpm/lib/oeqa/runtime/cases/tpm2.py +++ b/meta-tpm/lib/oeqa/runtime/cases/tpm2.py @@ -1,11 +1,19 @@ -# Copyright (C) 2019 Armin Kuster <akuster808@...> +# Copyright (C) 2019 - 2022 Armin Kuster <akuster808@...> # from oeqa.runtime.case import OERuntimeTestCase from oeqa.core.decorator.depends import OETestDepends from oeqa.runtime.decorator.package import OEHasPackage - +from oeqa.core.decorator.data import skipIfNotFeature class Tpm2Test(OERuntimeTestCase): + @classmethod + def setUpClass(cls): + cls.tc.target.run('mkdir /tmp/myvtpm2') + + @classmethod + def tearDownClass(cls): + cls.tc.target.run('rm -fr /tmp/myvtpm2') + def check_endlines(self, results, expected_endlines): for line in results.splitlines(): for el in expected_endlines: @@ -19,20 +27,19 @@ class Tpm2Test(OERuntimeTestCase): @OEHasPackage(['tpm2-tools']) @OEHasPackage(['tpm2-abrmd']) @OEHasPackage(['swtpm']) + @skipIfNotFeature('tpm2','Test tpm2_startup requires tpm2 to be in DISTRO_FEATURES') @OETestDepends(['ssh.SSHTest.test_ssh']) - def test_tpm2_swtpm_socket(self): + def test_tpm2_startup(self): cmds = [ - 'mkdir /tmp/myvtpm', - 'swtpm socket --tpmstate dir=/tmp/myvtpm --tpm2 --ctrl type=tcp,port=2322 --server type=tcp,port=2321 --flags not-need-init &', - 'export TPM2TOOLS_TCTI="swtpm:port=2321"', - 'tpm2_startup -c' + 'swtpm socket -d --tpmstate dir=/tmp/myvtpm2 --tpm2 --ctrl type=tcp,port=2322 --server type=tcp,port=2321 --flags not-need-init', + 'tpm2_startup -c -T "swtpm:port=2321"', ] for cmd in cmds: status, output = self.target.run(cmd) self.assertEqual(status, 0, msg='\n'.join([cmd, output])) - @OETestDepends(['tpm2.Tpm2Test.test_tpm2_swtpm_socket']) + @OETestDepends(['tpm2.Tpm2Test.test_tpm2_startup']) def test_tpm2_pcrread(self): (status, output) = self.target.run('tpm2_pcrread') expected_endlines = [] @@ -49,7 +56,7 @@ class Tpm2Test(OERuntimeTestCase): @OEHasPackage(['p11-kit']) @OEHasPackage(['tpm2-pkcs11']) - @OETestDepends(['tpm2.Tpm2Test.test_tpm2_swtpm_socket']) + @OETestDepends(['tpm2.Tpm2Test.test_tpm2_pcrread']) def test_tpm2_pkcs11(self): (status, output) = self.target.run('p11-kit list-modules -v') self.assertEqual(status, 0, msg="Modules missing: %s" % output) -- 2.37.3
|
|
[kirkstone][meta-tpm][PATCH 1/3] oeqa/swtpm: add swtpm runtime

Armin Kuster
Signed-off-by: Armin Kuster <akuster808@...> (cherry picked from commit 50eff83d428598630d5277904eeeb4b668c31c22) Signed-off-by: Armin Kuster <akuster808@...> --- meta-tpm/lib/oeqa/runtime/cases/swtpm.py | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 meta-tpm/lib/oeqa/runtime/cases/swtpm.py
diff --git a/meta-tpm/lib/oeqa/runtime/cases/swtpm.py b/meta-tpm/lib/oeqa/runtime/cases/swtpm.py new file mode 100644 index 0000000..df47b35 --- /dev/null +++ b/meta-tpm/lib/oeqa/runtime/cases/swtpm.py @@ -0,0 +1,24 @@ +# Copyright (C) 2022 Armin Kuster <akuster808@...> +# +from oeqa.runtime.case import OERuntimeTestCase +from oeqa.core.decorator.depends import OETestDepends +from oeqa.runtime.decorator.package import OEHasPackage +from oeqa.core.decorator.data import skipIfNotFeature + +class SwTpmTest(OERuntimeTestCase): + @classmethod + def setUpClass(cls): + cls.tc.target.run('mkdir /tmp/myvtpm2') + cls.tc.target.run('chown tss:root /tmp/myvtpm2') + + @classmethod + def tearDownClass(cls): + cls.tc.target.run('rm -fr /tmp/myvtpm2') + + @skipIfNotFeature('tpm2','Test tpm2_swtpm_socket requires tpm2 to be in DISTRO_FEATURES') + @OETestDepends(['ssh.SSHTest.test_ssh']) + @OEHasPackage(['swtpm']) + def test_swtpm2_ek_cert(self): + cmd = 'swtpm_setup --tpmstate /tmp/myvtpm2 --create-ek-cert --create-platform-cert --tpm2', + status, output = self.target.run(cmd) + self.assertEqual(status, 0, msg="swtpm create-ek-cert failed: %s" % output) -- 2.37.3
|
|
Re: [meta-security][PATCH] linux-yocto: drop version from bbappends

Armin Kuster
On 1/30/23 6:01 AM, Mikko Rapeli wrote: These bbappends apply to multiple kernel versions so no need to make them version dependent. Fixes recipe parsing when using meta-security master branch on kirkstone. In our custom layer we set layer compatibility for kirkstone and I understand why meta-security upstream would not want to do that:
LAYERSERIES_COMPAT_security-layer += 'kirkstone' LAYERSERIES_COMPAT_parsec-layer += 'kirkstone' LAYERSERIES_COMPAT_tpm-layer += 'kirkstone'
While I work towards supporting also yocto master branch and newer releases than kirkstone, I would appreciate if I would not have to branch off layers over minor details like this. Is this a dup of the one sent earlier? -armin Signed-off-by: Mikko Rapeli <mikko.rapeli@...> --- .../linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend} | 0 .../linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend} | 0 2 files changed, 0 insertions(+), 0 deletions(-) rename meta-tpm/recipes-kernel/linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend} (100%) rename recipes-kernel/linux/{linux-yocto_6.%.bbappend => linux-yocto_%.bbappend} (100%)
diff --git a/meta-tpm/recipes-kernel/linux/linux-yocto_6.%.bbappend b/meta-tpm/recipes-kernel/linux/linux-yocto_%.bbappend similarity index 100% rename from meta-tpm/recipes-kernel/linux/linux-yocto_6.%.bbappend rename to meta-tpm/recipes-kernel/linux/linux-yocto_%.bbappend diff --git a/recipes-kernel/linux/linux-yocto_6.%.bbappend b/recipes-kernel/linux/linux-yocto_%.bbappend similarity index 100% rename from recipes-kernel/linux/linux-yocto_6.%.bbappend rename to recipes-kernel/linux/linux-yocto_%.bbappend
|
|
Re: QA notification for completed autobuilder build (yocto-4.0.7.rc1)
Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-4.0.7.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. NUC 7 3. ADL 4. TGL NUC 11 5. Edgerouter 6. Beaglebone ETA for completion next Monday, Feb 3. Best regards, Jing Hui
toggle quoted message
Show quoted text
-----Original Message----- From: yocto@... <yocto@...> On Behalf Of Pokybuild User Sent: Saturday, 28 January, 2023 7:09 AM To: yocto@... Cc: qa-build-notification@... Subject: [yocto] QA notification for completed autobuilder build (yocto-4.0.7.rc1)
A build flagged for QA (yocto-4.0.7.rc1) was completed on the autobuilder and is available at:
https://autobuilder.yocto.io/pub/releases/yocto-4.0.7.rc1
Build hash information:
bitbake: 7e268c107bb0240d583d2c34e24a71e373382509 meta-agl: b9d4796f44a56c6a9c8233d82e46c251a82f6020 meta-arm: ce41be0a7fe7c6f5fd2155866980388d3c83389f meta-aws: 9d9400b03c22839398756f505491718392907266 meta-gplv2: d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a meta-intel: f529e0594a784546926e89ce8e78385e00d0b0a9 meta-mingw: a90614a6498c3345704e9611f2842eb933dc51c1 meta-openembedded: 1f31570d0795da90083d1dbf28127c90908e30ee meta-virtualization: 9a94fa2ad76990b0eca40837a98aaf4cd83a7248 oecore: a8c82902384f7430519a31732a4bb631f21693ac poky: 65dafea22018052fe7b2e17e6e4d7eb754224d38
This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.purdie@...
|
|
Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-4.2_M2.rc2)
toggle quoted message
Show quoted text
-----Original Message----- From: qa-build-notification@... <qa-build- notification@...> On Behalf Of Pokybuild User Sent: Friday, 27 January, 2023 1:13 PM To: yocto@... Cc: qa-build-notification@... Subject: [qa-build-notification] QA notification for completed autobuilder build (yocto-4.2_M2.rc2)
A build flagged for QA (yocto-4.2_M2.rc2) was completed on the autobuilder and is available at:
https://autobuilder.yocto.io/pub/releases/yocto-4.2_M2.rc2
Build hash information:
bitbake: c19035e8e71c419c5688a86bfc9c946c96f638e8 meta-agl: 09135164a21a216c6e3e75d7decce896b92962f0 meta-arm: d8383c11f3f8220d2b989ec73604e5faff988299 meta-aws: 7b4f54b3e1f675e2033f6a589ac519e44e62b58b meta-intel: b3c7d3ee44e4ab71df44b5be3c48d2f47d89d8a0 meta-mingw: 250617ffa524c082b848487359b9d045703d59c2 meta-openembedded: ceceffcb1e3ef4f9ba7708f77c27e30a7aea61e5 meta-virtualization: 31954471605ae3b41627a0ab7b0dcfe8c5851bd7 oecore: 493f2d163718d78560a2b3ad5d3c0fb34caae8c0 poky: 5e249ec855517765f4b99e8039cb888ffa09c211
This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.purdie@...
|
|
Re: Error while adding " libimxvpuapi2" and "gstreamer" pkgs in my local.conf for imx8mplus
Hi All If the imx8mp encoder is fully backward compatible with the imx8mm encoder, then PLATFORM:mx8mp-nxp-bsp = "IMX8MP" defined in imx-vpu-hantro_1.27.0.bb to PLATFORM:mx8mp-nxp-bsp = "IMX8MM" in the bbappend file, the header file for hantro_h1 that the source code for the encoder in libimxvpuapi2 refers to, and that is used when linking It is confirmed that libhantro_h1.so is extracted under resipe-sysroot of libimxvpuapi2. I have not been able to confirm the compatibility of hantro_h1 and hantro_vc8000e, so please use at your own risk. Create the libimxvpuapi2_%.bbappen file and add IMX_PLATFOEM:mx8mp-nxp-bsp = "imx8m"
I think this is perhaps in right direction but I would suggest
IMX_PLATFORM:mx8mp-nxp-bsp = "imx8mm"
On 2023/01/31 17:40, Khem Raj wrote: On Mon, Jan 30, 2023 at 6:34 PM Takayasu Ito <ito@...> wrote:
Hi Nikita
The problem is that in the imx-vpu-hantro recipe, the encoder library, libhantro_h1.so, is not installed for mx8mp, but is installed for mx8mm.
In the libimxvpuapi2 recipe, imx8mp specifies imx8mm in IMX_PLATFORM. Therefore, the _encoder variable used in the waf wsctipt file is set to true, so a check is made for the presence of hantro_h1, resulting in an error. At this time, libimxvpuapi2 support for imx8m is imx8m and imx8mm, so by changing the setting to one for imx8m, which does not use a hardware encoder, the build for imx8mp will pass.
Create the libimxvpuapi2_%.bbappen file and add IMX_PLATFOEM:mx8mp-nxp-bsp = "imx8m"
I think this is perhaps in right direction but I would suggest IMX_PLATFORM:mx8mp-nxp-bsp = "imx8mm"
Translated with www.DeepL.com/Translator (free version) On 2023/01/30 20:19, Nikita Gupta wrote:
Hello Takayasu Thanks for your suggestion, but after implementing i am facing same thing (see attached image).
Regards Nikita Gupta
On Fri, 27 Jan 2023 at 17:55, Takayasu Ito <ito@... <mailto:ito@...>> wrote:
Hi Nikita
> *IMAGE_INSTALL:append = "gstreamer1.0 gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-bad
If you do not put a space after the double quotation marks, the package names before and after will be attached to each other during the merge.
See https://docs.yoctoproject.org/bitbake/2.2/bitbake-user-manual/bitbake-user-manual-metadata.html#appending-and-prepending-override-style-syntax <https://docs.yoctoproject.org/bitbake/2.2/bitbake-user-manual/bitbake-user-manual-metadata.html#appending-and-prepending-override-style-syntax>
On 2023/01/27 20:48, Nikita Gupta wrote: > Hello List, > > As i earlier mentioned that i want to do some customisation in local.conf by adding few pkgs (below). > *IMAGE_INSTALL:append = "gstreamer1.0 gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-bad > gstreamer1.0-plugins-ugly gstreamer1.0-libav imx-vpuwrap imx-gpu-g2d imx-gpu-viv gstreamer1.0-plugins-imx imx-gst1.0-plugin" > LICENSE_FLAGS_ACCEPTED = " commercial" > IMAGE_INSTALL:append = "kernel-devsrc" > IMAGE_INSTALL:append = "gstreamer1.0-rtsp-server gst-variable-rtsp-server" > IMAGE_INSTALL:append = " gtk+3" > CORE_IMAGE_EXTRA_INSTALL += " opencv libopencv-core-dev libopencv-highgui-dev libopencv-imgproc-dev libopencv-objdetect-dev > libopencv-ml-dev" > #LICENSE_FLAGS_WHITELIST = " commercial" > IMAGE_ROOTFS_EXTRA_SPACE = "1048576 "* > and iafter bitbake m getting below errors. > > nikita@nikita-HP-Laptop-15-bs0xx:~/Yocto/imx-yocto-bsp$ *bitbake imx-image-full* > Loading cache: 100% |##########################################################################################################| > Time: 0:00:01 > Loaded 4736 entries from dependency cache. > Parsing recipes: 100% |########################################################################################################| > Time: 0:00:02 > Parsing of 3190 .bb files complete (3188 cached, 2 parsed). 4738 targets, 262 skipped, 3 masked, 0 errors. > NOTE: Resolving any missing task queue dependencies > ERROR: Nothing RPROVIDES 'imx-gst1.0-pluginkernel-devsrcgstreamer1.0-rtsp-server' (but > /home/nikita/Yocto/imx-yocto-bsp/sources/meta-imx/meta-sdk/dynamic-layers/qt6-layer/recipes-fsl/images/imx-image-full.bb <http://imx-image-full.bb> > <http://imx-image-full.bb <http://imx-image-full.bb>> RDEPENDS on or otherwise requires it) > NOTE: Runtime target 'imx-gst1.0-pluginkernel-devsrcgstreamer1.0-rtsp-server' is unbuildable, removing... > Missing or unbuildable dependency chain was: ['imx-gst1.0-pluginkernel-devsrcgstreamer1.0-rtsp-server'] > ERROR: Required build target 'imx-image-full' has no buildable providers. > Missing or unbuildable dependency chain was: ['imx-image-full', 'imx-gst1.0-pluginkernel-devsrcgstreamer1.0-rtsp-server'] > > Summary: There were 2 ERROR messages, returning a non-zero exit code. > > These packages are needed i can not remove So please help me what can i do in this. > > Thanks in Advance. > > On Fri, 27 Jan 2023 at 17:00, Nikita Gupta <nikitagupta2509@... <mailto:nikitagupta2509@...> <mailto:nikitagupta2509@... <mailto:nikitagupta2509@...>>> wrote: > > Hello Alex > > When i run bitbake libimxvpuapi2 and it shows below error (images attached). > Can you please tell me that is "libimxvpuapi2" compatible with imx8mplus board? > > Thanks in Advance > > On Fri, 27 Jan 2023 at 14:35, Alexander Kanavin <alex.kanavin@... <mailto:alex.kanavin@...> <mailto:alex.kanavin@... <mailto:alex.kanavin@...>>> wrote: > > The screenshot indicates the problem originates in libimxvpuapi2 > recipe. So you should get more information by running 'bitbake > libimxvpuapi2'. > > Alex > > On Fri, 27 Jan 2023 at 07:46, Nikita Gupta <nikitagupta2509@... <mailto:nikitagupta2509@...> <mailto:nikitagupta2509@... <mailto:nikitagupta2509@...>>> wrote: > > > > Hello Alexander > > > > I am not getting your query . Can u please explain your question? > > > > Regards > > Nikita Gupta > > > > On Wed, Jan 25, 2023, 18:35 Alexander Kanavin <alex.kanavin@... <mailto:alex.kanavin@...> <mailto:alex.kanavin@... <mailto:alex.kanavin@...>>> wrote: > >> > >> What happens if you bitbake libimx… thingy directly? > >> > >> Alex > >> > >> On Wed 25. Jan 2023 at 13.47, Nikita Gupta <nikitagupta2509@... <mailto:nikitagupta2509@...> <mailto:nikitagupta2509@... <mailto:nikitagupta2509@...>>> wrote: > >>> > >>> Hello list, > >>> > >>> I was just making image for imx8mplus by adding few pkgs in my local.conf but encountered few errors so i am here > for your help. > >>> I added below pkgs in my local.conf file > >>> > >>> IMAGE_INSTALL:append = "gstreamer1.0 gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-bad > gstreamer1.0-plugins-ugly gstreamer1.0-libav imx-vpuwrap imx-gpu-g2d imx-gpu-viv gstreamer1.0-plugins-imx > imx-gst1.0-plugin" > >>> LICENSE_FLAGS_WHITELIST = "commercial" > >>> IMAGE_INSTALL:append = "kernel-devsrc" > >>> IMAGE_INSTALL_append += "gstreamer1.0-rtsp-server gst-variable-rtsp-server" > >>> IMAGE_INSTALL:append = " gtk+3" > >>> CORE_IMAGE_EXTRA_INSTALL += " opencv libopencv-core-dev libopencv-highgui-dev libopencv-imgproc-dev > libopencv-objdetect-dev libopencv-ml-dev" > >>> IMAGE_ROOTFS_EXTRA_SPACE = "1048576 " > >>> > >>> So my local.conf file now looks like this > >>> So i am getting below error after baking my recipe ( Attached image). > >>> > >>> Please tell what should I need to do to resolve this. > >>> > >>> Thanks in advance > >>> > >>> > >>> > > > > >
-- Takayasu Ito Solution Department, Lineo Solutions, Inc. https://www.lineo.co.jp/english/ <https://www.lineo.co.jp/english/> Email: ito@... <mailto:ito@...> Yocto Project Ambassador
-- Takayasu Ito Yocto Project Ambassador Solution Department Lineo Solutions, Inc. https://www.lineo.co.jp/english/ Email: ito@...
-- Takayasu Ito Yocto Project Ambassador Solution Department Lineo Solutions, Inc. https://www.lineo.co.jp/english/Email: ito@...
|
|
Re: [meta-raspberrypi] Is Preempt-rt still supported in master / latest releases?
#raspberrypi
Hello Lukasz, Aleksandr,
I have not managed to build it for Rpi4-64. I followed the same approach as Aleksandr but it does not work for 64bit system.
Doing exactly the same changes as Aleksandr if I build for MACHINE = "raspberrypi4-64" in local.conf, the .config file has following configs: CONFIG_HAVE_PREEMPT_LAZY=y CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set
If in the local.conf I replace the machine to MACHINE = "raspberrypi4" and I bitbake again, the .config file looks as follow: CONFIG_HAVE_PREEMPT_LAZY=y CONFIG_PREEMPT_LAZY=y # CONFIG_PREEMPT_NONE is not set # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set CONFIG_PREEMPT_RT=y CONFIG_PREEMPT_COUNT=y CONFIG_PREEMPTION=y
So for raspberrypi4 the RT kernel is built whereas for raspberrypi4-64 a non preemptive kernel is built (without adding rt.cfg or the patch a PREEMPTIVE kernel will be built, i.e. CONFIG_PREEMPT=y is set in the .config file).
Once I figure out why this happens I will post it here. Any further hints are appreciated.
Best Regards, Carles
|
|
Re: Setting recipe PACKAGECONFIG with in a Bash script?

Rudolf J Streif
Hello, On 1/31/23 05:34, Electronic Consult wrote: Hello, I've searched & can't seem to find an answer for this but I'm sure it must have come up before.
I'd like to automate the generating of images using Bash & create similar recipes but with different PACKAGECONFIG's. How does one do that?
PACKAGECONFIG is to enable/disable features for a particular software package on a per-recipe basis. Hence, by its nature, PACKAGECONFIG is a recipe local variable. If you want to set it in a global configuration file you need to use the syntax: PACKAGECONFIG:pn-<recipename> = "feature1 feature3" if you want to override the entire PACKAGECONFIG variable, or PACKAGECONFIG:append:pn-<recipename> = "feature4" if you want to add to the configuration. It would be something like:
#! /bin/bash source oe-init-build-env build-microchip
# Generate first image PACKAGECONFIG = "foo" MACHINE=sama5d4-xplained-sd bitbake microchip-graphics-images # Upload image to 'cloud' mv sama5d4-xplained-sd /theCloud
# Generate second image PACKAGECONFIG = "bar" MACHINE=sama5d4-xplained-sd bitbake microchip-graphics-images # Upload image to 'cloud' mv sama5d4-xplained-sd /theCloud
For this I would add the specific PACKAGECONFIG to a bitbake pre- or post-configuration file and call: bitbake -r preconf ... bitbake -R postconf ... Thanks,
-- Rudolf J Streif CEO/CTO 1.855.442.3386
|
|
Re: [OE-core] Yocto Project Status 31 January 2023 (WW05)
On Tue, 31 Jan 2023 at 15:14, Stephen Jolley <sjolley.yp.pm@...> wrote: Key Status/Updates:
YP 4.0.7 and YP 4.2 M2 are in QA We switched to the 6.1 kernel by default for M2. Unfortunately there are a couple of intermittent issues that seem to have crept in. One is a reproducibility issue in perf, likely with some host component causing it as it only occurs on second builds. The second appears to be an intermittent networking issue accessing a python http-server for testing dnf which appeared after the kernel version change. We are continuing to see other intermittent failures which are limiting how quickly we can merge changes. A summary of some of the key issues was sent to the mailing list: https://lists.openembedded.org/g/openembedded-core/message/176476 There have been changes to the way the codeparser cache in bitbake stores data which should reduce cache size, reduce the times data needs to be written out and generally help performance. CVE levels in master are still high but there are patches in progress for most issues as I understand it. We have a growing number of bugs in bugzilla, any help with them is appreciated. Please do notice there's a new public article by RP: https://www.linux.com/audience/maintainer-confidential-opportunities-and-challenges-of-the-ubiquitous-but-under-resourced-yocto-project/"Maintainer confidential: Opportunities and challenges of the ubiquitous but under-resourced Yocto Project. Maintainers are an important topic of discussion. I’ve read a few perspectives, but I’d like to share mine as one of the lesser-known maintainers in the open source world." LWN has picked it up as well: https://lwn.net/Articles/921646(many of the comments are the usual 'yocto is hard' fare, which should be treated like the weather - inevitable) Alex Alex
|
|
Re: Adding openjdk-11 to Yocto
On Jan 30, 2023, at 12:27 PM, Richard Leitner <richard.leitner@...> wrote:
Hi David, unfortunately none I'm aware of.
But if you have time to add java 11 (or newer) support to meta-java I can give support/guidance.
regards;rl Is there any interest in adding recipes that install pre-built Java binaries to meta-java? I needed a newer Java and the easy way was to make a recipe to install the Adoptium binaries: https://github.com/bobolopolis/meta-adoptium/blob/main/recipes-core/temurin/temurin-jdk-17-bin_17.0.6%2B10.bbThis was fine for my purposes, but obviously there’s tradeoffs to using someones pre-built binary. I can send a patch to add these to meta-java if it would be useful to others. Thanks, Robert
|
|
Yocto Project Status 31 January 2023 (WW05)
Current Dev Position: YP 4.2 M3 Next Deadline: 20th February 2023 YP 4.2 M3 Build Next Team Meetings: Key Status/Updates: - YP 4.0.7 and YP 4.2 M2 are in QA
- We switched to the 6.1 kernel by default for M2. Unfortunately there are a couple of intermittent issues that seem to have crept in. One is a reproducibility issue in perf, likely with some host component causing it as it only occurs on second builds. The second appears to be an intermittent networking issue accessing a python http-server for testing dnf which appeared after the kernel version change.
- We are continuing to see other intermittent failures which are limiting how quickly we can merge changes. A summary of some of the key issues was sent to the mailing list: https://lists.openembedded.org/g/openembedded-core/message/176476
- There have been changes to the way the codeparser cache in bitbake stores data which should reduce cache size, reduce the times data needs to be written out and generally help performance.
- CVE levels in master are still high but there are patches in progress for most issues as I understand it.
- We have a growing number of bugs in bugzilla, any help with them is appreciated.
Ways to contribute: - As people are likely aware, the project has a number of components which are either unmaintained, or have people with little to no time trying to keep them alive. These components include: patchtest, layerindex, devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help is welcome in trying to better look after these components!
- 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 4.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_Unassigned_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 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 is very much welcome in trying to resolve our autobuilder intermittent issues. 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.
- Help us resolve CVE issues: CVE metrics
YP 4.2 Milestone Dates: - YP 4.2 M2 built and in QA
- YP 4.2 M3 build date 2023/02/20
- YP 4.2 M3 Release date 2023/03/03
- YP 4.2 M4 build date 2023/04/03
- YP 4.2 M4 Release date 2023/04/28
Upcoming dot releases: - YP 4.0.7 built and in QA
- YP 3.1.23 build date 2023/02/13
- YP 3.1.23 Release date 2023/02/24
- YP 4.0.8 build date 2023/02/27
- YP 4.0.8 Release date 2023/03/10
- YP 4.1.3 build date 2023/03/06
- YP 4.1.3 Release date 2023/03/17
- YP 3.1.24 build date 2023/03/20
- YP 3.1.24 Release date 2023/03/31
- YP 4.0.9 build date 2023/04/10
- YP 4.0.9 Release date 2023/04/21
- YP 4.1.4 build date 2023/05/01
- YP 4.1.4 Release date 2023/05/13
- YP 3.1.25 build date 2023/05/08
- YP 3.1.25 Release date 2023/05/19
- YP 4.0.10 build date 2023/05/15
- YP 4.0.10 Release date 2023/05/26
Tracking Metrics: The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at: https://wiki.yoctoproject.org/wiki/TSC The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status [If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!] Thanks, Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
|
Setting recipe PACKAGECONFIG with in a Bash script?
Hello, I've searched & can't seem to find an answer for this but I'm sure it must have come up before.
I'd like to automate the generating of images using Bash & create similar recipes but with different PACKAGECONFIG's. How does one do that?
It would be something like:
#! /bin/bash source oe-init-build-env build-microchip
# Generate first image PACKAGECONFIG = "foo" MACHINE=sama5d4-xplained-sd bitbake microchip-graphics-images # Upload image to 'cloud' mv sama5d4-xplained-sd /theCloud
# Generate second image PACKAGECONFIG = "bar" MACHINE=sama5d4-xplained-sd bitbake microchip-graphics-images # Upload image to 'cloud' mv sama5d4-xplained-sd /theCloud
Thanks,
|
|
Re: Error while adding " libimxvpuapi2" and "gstreamer" pkgs in my local.conf for imx8mplus
Nikita Gupta <nikitagupta2509@...>
Hello All, I created one libimxvpuapi2_%.bbappend file in "libimxvpuapi" directory and following platform configuration in that and it works. IMX_PLATFORM:mx8mp-nxp-bsp = "imx8m"
Thanks team for this kind help.
toggle quoted message
Show quoted text
On Tue, 31 Jan 2023 at 14:11, Khem Raj < raj.khem@...> wrote: On Mon, Jan 30, 2023 at 6:34 PM Takayasu Ito <ito@...> wrote:
>
> Hi Nikita
>
> The problem is that in the imx-vpu-hantro recipe, the encoder library,
> libhantro_h1.so, is not installed for mx8mp, but is installed for mx8mm.
>
> In the libimxvpuapi2 recipe, imx8mp specifies imx8mm in IMX_PLATFORM.
> Therefore, the _encoder variable used in the waf wsctipt file is set to
> true, so a check is made for the presence of hantro_h1, resulting in an
> error.
> At this time, libimxvpuapi2 support for imx8m is imx8m and imx8mm, so by
> changing the setting to one for imx8m, which does not use a hardware
> encoder, the build for imx8mp will pass.
>
> Create the libimxvpuapi2_%.bbappen file and add
> IMX_PLATFOEM:mx8mp-nxp-bsp = "imx8m"
>
I think this is perhaps in right direction but I would suggest
IMX_PLATFORM:mx8mp-nxp-bsp = "imx8mm"
>
>
> Translated with www.DeepL.com/Translator (free version)
> On 2023/01/30 20:19, Nikita Gupta wrote:
> > Hello Takayasu
> > Thanks for your suggestion, but after implementing i am facing same
> > thing (see attached image).
> >
> > Regards
> > Nikita Gupta
> >
> > On Fri, 27 Jan 2023 at 17:55, Takayasu Ito <ito@...
> > <mailto:ito@...>> wrote:
> >
> > Hi Nikita
> >
> > > *IMAGE_INSTALL:append = "gstreamer1.0 gstreamer1.0-plugins-base
> > gstreamer1.0-plugins-good gstreamer1.0-plugins-bad
> >
> > If you do not put a space after the double quotation marks, the
> > package names before and after will be attached to each other
> > during the merge.
> >
> > See
> > https://docs.yoctoproject.org/bitbake/2.2/bitbake-user-manual/bitbake-user-manual-metadata.html#appending-and-prepending-override-style-syntax <https://docs.yoctoproject.org/bitbake/2.2/bitbake-user-manual/bitbake-user-manual-metadata.html#appending-and-prepending-override-style-syntax>
> >
> > On 2023/01/27 20:48, Nikita Gupta wrote:
> > > Hello List,
> > >
> > > As i earlier mentioned that i want to do some customisation in
> > local.conf by adding few pkgs (below).
> > > *IMAGE_INSTALL:append = "gstreamer1.0 gstreamer1.0-plugins-base
> > gstreamer1.0-plugins-good gstreamer1.0-plugins-bad
> > > gstreamer1.0-plugins-ugly gstreamer1.0-libav imx-vpuwrap
> > imx-gpu-g2d imx-gpu-viv gstreamer1.0-plugins-imx imx-gst1.0-plugin"
> > > LICENSE_FLAGS_ACCEPTED = " commercial"
> > > IMAGE_INSTALL:append = "kernel-devsrc"
> > > IMAGE_INSTALL:append = "gstreamer1.0-rtsp-server
> > gst-variable-rtsp-server"
> > > IMAGE_INSTALL:append = " gtk+3"
> > > CORE_IMAGE_EXTRA_INSTALL += " opencv libopencv-core-dev
> > libopencv-highgui-dev libopencv-imgproc-dev libopencv-objdetect-dev
> > > libopencv-ml-dev"
> > > #LICENSE_FLAGS_WHITELIST = " commercial"
> > > IMAGE_ROOTFS_EXTRA_SPACE = "1048576 "*
> > > and iafter bitbake m getting below errors.
> > >
> > > nikita@nikita-HP-Laptop-15-bs0xx:~/Yocto/imx-yocto-bsp$ *bitbake
> > imx-image-full*
> > > Loading cache: 100%
> > |##########################################################################################################|
> > > Time: 0:00:01
> > > Loaded 4736 entries from dependency cache.
> > > Parsing recipes: 100%
> > |########################################################################################################|
> > > Time: 0:00:02
> > > Parsing of 3190 .bb files complete (3188 cached, 2 parsed). 4738
> > targets, 262 skipped, 3 masked, 0 errors.
> > > NOTE: Resolving any missing task queue dependencies
> > > ERROR: Nothing RPROVIDES
> > 'imx-gst1.0-pluginkernel-devsrcgstreamer1.0-rtsp-server' (but
> > >
> > /home/nikita/Yocto/imx-yocto-bsp/sources/meta-imx/meta-sdk/dynamic-layers/qt6-layer/recipes-fsl/images/imx-image-full.bb <http://imx-image-full.bb>
> > > <http://imx-image-full.bb <http://imx-image-full.bb>> RDEPENDS on
> > or otherwise requires it)
> > > NOTE: Runtime target
> > 'imx-gst1.0-pluginkernel-devsrcgstreamer1.0-rtsp-server' is
> > unbuildable, removing...
> > > Missing or unbuildable dependency chain was:
> > ['imx-gst1.0-pluginkernel-devsrcgstreamer1.0-rtsp-server']
> > > ERROR: Required build target 'imx-image-full' has no buildable
> > providers.
> > > Missing or unbuildable dependency chain was: ['imx-image-full',
> > 'imx-gst1.0-pluginkernel-devsrcgstreamer1.0-rtsp-server']
> > >
> > > Summary: There were 2 ERROR messages, returning a non-zero exit code.
> > >
> > > These packages are needed i can not remove So please help me what
> > can i do in this.
> > >
> > > Thanks in Advance.
> > >
> > > On Fri, 27 Jan 2023 at 17:00, Nikita Gupta
> > <nikitagupta2509@... <mailto:nikitagupta2509@...>
> > <mailto:nikitagupta2509@...
> > <mailto:nikitagupta2509@...>>> wrote:
> > >
> > > Hello Alex
> > >
> > > When i run bitbake libimxvpuapi2 and it shows below error
> > (images attached).
> > > Can you please tell me that is "libimxvpuapi2" compatible
> > with imx8mplus board?
> > >
> > > Thanks in Advance
> > >
> > > On Fri, 27 Jan 2023 at 14:35, Alexander Kanavin
> > <alex.kanavin@... <mailto:alex.kanavin@...>
> > <mailto:alex.kanavin@... <mailto:alex.kanavin@...>>> wrote:
> > >
> > > The screenshot indicates the problem originates in
> > libimxvpuapi2
> > > recipe. So you should get more information by running
> > 'bitbake
> > > libimxvpuapi2'.
> > >
> > > Alex
> > >
> > > On Fri, 27 Jan 2023 at 07:46, Nikita Gupta
> > <nikitagupta2509@... <mailto:nikitagupta2509@...>
> > <mailto:nikitagupta2509@...
> > <mailto:nikitagupta2509@...>>> wrote:
> > > >
> > > > Hello Alexander
> > > >
> > > > I am not getting your query . Can u please explain
> > your question?
> > > >
> > > > Regards
> > > > Nikita Gupta
> > > >
> > > > On Wed, Jan 25, 2023, 18:35 Alexander Kanavin
> > <alex.kanavin@... <mailto:alex.kanavin@...>
> > <mailto:alex.kanavin@... <mailto:alex.kanavin@...>>> wrote:
> > > >>
> > > >> What happens if you bitbake libimx… thingy directly?
> > > >>
> > > >> Alex
> > > >>
> > > >> On Wed 25. Jan 2023 at 13.47, Nikita Gupta
> > <nikitagupta2509@... <mailto:nikitagupta2509@...>
> > <mailto:nikitagupta2509@...
> > <mailto:nikitagupta2509@...>>> wrote:
> > > >>>
> > > >>> Hello list,
> > > >>>
> > > >>> I was just making image for imx8mplus by adding few
> > pkgs in my local.conf but encountered few errors so i am here
> > > for your help.
> > > >>> I added below pkgs in my local.conf file
> > > >>>
> > > >>> IMAGE_INSTALL:append = "gstreamer1.0
> > gstreamer1.0-plugins-base gstreamer1.0-plugins-good
> > gstreamer1.0-plugins-bad
> > > gstreamer1.0-plugins-ugly gstreamer1.0-libav imx-vpuwrap
> > imx-gpu-g2d imx-gpu-viv gstreamer1.0-plugins-imx
> > > imx-gst1.0-plugin"
> > > >>> LICENSE_FLAGS_WHITELIST = "commercial"
> > > >>> IMAGE_INSTALL:append = "kernel-devsrc"
> > > >>> IMAGE_INSTALL_append += "gstreamer1.0-rtsp-server
> > gst-variable-rtsp-server"
> > > >>> IMAGE_INSTALL:append = " gtk+3"
> > > >>> CORE_IMAGE_EXTRA_INSTALL += " opencv
> > libopencv-core-dev libopencv-highgui-dev libopencv-imgproc-dev
> > > libopencv-objdetect-dev libopencv-ml-dev"
> > > >>> IMAGE_ROOTFS_EXTRA_SPACE = "1048576 "
> > > >>>
> > > >>> So my local.conf file now looks like this
> > > >>> So i am getting below error after baking my recipe (
> > Attached image).
> > > >>>
> > > >>> Please tell what should I need to do to resolve this.
> > > >>>
> > > >>> Thanks in advance
> > > >>>
> > > >>>
> > > >>>
> > >
> > >
> > >
> > >
> > >
> >
> > --
> > Takayasu Ito
> > Solution Department, Lineo Solutions, Inc.
> > https://www.lineo.co.jp/english/ <https://www.lineo.co.jp/english/>
> > Email: ito@... <mailto:ito@...>
> > Yocto Project Ambassador
> >
>
> --
> Takayasu Ito
> Yocto Project Ambassador
> Solution Department Lineo Solutions, Inc.
> https://www.lineo.co.jp/english/
> Email: ito@...
>
>
>
>
|
|
Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-4.2_M2.rc2)
Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-4.2_M2.rc2. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. NUC 7 3. ADL 4. TGL NUC 11 5. Edgerouter 6. Beaglebone ETA for completion Wednesday, 1st Feb. Best regards, Jing Hui
toggle quoted message
Show quoted text
-----Original Message----- From: qa-build-notification@... <qa-build- notification@...> On Behalf Of Pokybuild User Sent: Friday, 27 January, 2023 1:13 PM To: yocto@... Cc: qa-build-notification@... Subject: [qa-build-notification] QA notification for completed autobuilder build (yocto-4.2_M2.rc2)
A build flagged for QA (yocto-4.2_M2.rc2) was completed on the autobuilder and is available at:
https://autobuilder.yocto.io/pub/releases/yocto-4.2_M2.rc2
Build hash information:
bitbake: c19035e8e71c419c5688a86bfc9c946c96f638e8 meta-agl: 09135164a21a216c6e3e75d7decce896b92962f0 meta-arm: d8383c11f3f8220d2b989ec73604e5faff988299 meta-aws: 7b4f54b3e1f675e2033f6a589ac519e44e62b58b meta-intel: b3c7d3ee44e4ab71df44b5be3c48d2f47d89d8a0 meta-mingw: 250617ffa524c082b848487359b9d045703d59c2 meta-openembedded: ceceffcb1e3ef4f9ba7708f77c27e30a7aea61e5 meta-virtualization: 31954471605ae3b41627a0ab7b0dcfe8c5851bd7 oecore: 493f2d163718d78560a2b3ad5d3c0fb34caae8c0 poky: 5e249ec855517765f4b99e8039cb888ffa09c211
This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.purdie@...
|
|
Re: Error while adding " libimxvpuapi2" and "gstreamer" pkgs in my local.conf for imx8mplus

Khem Raj
On Mon, Jan 30, 2023 at 6:34 PM Takayasu Ito <ito@...> wrote: Hi Nikita
The problem is that in the imx-vpu-hantro recipe, the encoder library, libhantro_h1.so, is not installed for mx8mp, but is installed for mx8mm.
In the libimxvpuapi2 recipe, imx8mp specifies imx8mm in IMX_PLATFORM. Therefore, the _encoder variable used in the waf wsctipt file is set to true, so a check is made for the presence of hantro_h1, resulting in an error. At this time, libimxvpuapi2 support for imx8m is imx8m and imx8mm, so by changing the setting to one for imx8m, which does not use a hardware encoder, the build for imx8mp will pass.
Create the libimxvpuapi2_%.bbappen file and add IMX_PLATFOEM:mx8mp-nxp-bsp = "imx8m"
I think this is perhaps in right direction but I would suggest IMX_PLATFORM:mx8mp-nxp-bsp = "imx8mm"
Translated with www.DeepL.com/Translator (free version) On 2023/01/30 20:19, Nikita Gupta wrote:
Hello Takayasu Thanks for your suggestion, but after implementing i am facing same thing (see attached image).
Regards Nikita Gupta
On Fri, 27 Jan 2023 at 17:55, Takayasu Ito <ito@... <mailto:ito@...>> wrote:
Hi Nikita
> *IMAGE_INSTALL:append = "gstreamer1.0 gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-bad
If you do not put a space after the double quotation marks, the package names before and after will be attached to each other during the merge.
See https://docs.yoctoproject.org/bitbake/2.2/bitbake-user-manual/bitbake-user-manual-metadata.html#appending-and-prepending-override-style-syntax <https://docs.yoctoproject.org/bitbake/2.2/bitbake-user-manual/bitbake-user-manual-metadata.html#appending-and-prepending-override-style-syntax>
On 2023/01/27 20:48, Nikita Gupta wrote: > Hello List, > > As i earlier mentioned that i want to do some customisation in local.conf by adding few pkgs (below). > *IMAGE_INSTALL:append = "gstreamer1.0 gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-bad > gstreamer1.0-plugins-ugly gstreamer1.0-libav imx-vpuwrap imx-gpu-g2d imx-gpu-viv gstreamer1.0-plugins-imx imx-gst1.0-plugin" > LICENSE_FLAGS_ACCEPTED = " commercial" > IMAGE_INSTALL:append = "kernel-devsrc" > IMAGE_INSTALL:append = "gstreamer1.0-rtsp-server gst-variable-rtsp-server" > IMAGE_INSTALL:append = " gtk+3" > CORE_IMAGE_EXTRA_INSTALL += " opencv libopencv-core-dev libopencv-highgui-dev libopencv-imgproc-dev libopencv-objdetect-dev > libopencv-ml-dev" > #LICENSE_FLAGS_WHITELIST = " commercial" > IMAGE_ROOTFS_EXTRA_SPACE = "1048576 "* > and iafter bitbake m getting below errors. > > nikita@nikita-HP-Laptop-15-bs0xx:~/Yocto/imx-yocto-bsp$ *bitbake imx-image-full* > Loading cache: 100% |##########################################################################################################| > Time: 0:00:01 > Loaded 4736 entries from dependency cache. > Parsing recipes: 100% |########################################################################################################| > Time: 0:00:02 > Parsing of 3190 .bb files complete (3188 cached, 2 parsed). 4738 targets, 262 skipped, 3 masked, 0 errors. > NOTE: Resolving any missing task queue dependencies > ERROR: Nothing RPROVIDES 'imx-gst1.0-pluginkernel-devsrcgstreamer1.0-rtsp-server' (but > /home/nikita/Yocto/imx-yocto-bsp/sources/meta-imx/meta-sdk/dynamic-layers/qt6-layer/recipes-fsl/images/imx-image-full.bb <http://imx-image-full.bb> > <http://imx-image-full.bb <http://imx-image-full.bb>> RDEPENDS on or otherwise requires it) > NOTE: Runtime target 'imx-gst1.0-pluginkernel-devsrcgstreamer1.0-rtsp-server' is unbuildable, removing... > Missing or unbuildable dependency chain was: ['imx-gst1.0-pluginkernel-devsrcgstreamer1.0-rtsp-server'] > ERROR: Required build target 'imx-image-full' has no buildable providers. > Missing or unbuildable dependency chain was: ['imx-image-full', 'imx-gst1.0-pluginkernel-devsrcgstreamer1.0-rtsp-server'] > > Summary: There were 2 ERROR messages, returning a non-zero exit code. > > These packages are needed i can not remove So please help me what can i do in this. > > Thanks in Advance. > > On Fri, 27 Jan 2023 at 17:00, Nikita Gupta <nikitagupta2509@... <mailto:nikitagupta2509@...> <mailto:nikitagupta2509@... <mailto:nikitagupta2509@...>>> wrote: > > Hello Alex > > When i run bitbake libimxvpuapi2 and it shows below error (images attached). > Can you please tell me that is "libimxvpuapi2" compatible with imx8mplus board? > > Thanks in Advance > > On Fri, 27 Jan 2023 at 14:35, Alexander Kanavin <alex.kanavin@... <mailto:alex.kanavin@...> <mailto:alex.kanavin@... <mailto:alex.kanavin@...>>> wrote: > > The screenshot indicates the problem originates in libimxvpuapi2 > recipe. So you should get more information by running 'bitbake > libimxvpuapi2'. > > Alex > > On Fri, 27 Jan 2023 at 07:46, Nikita Gupta <nikitagupta2509@... <mailto:nikitagupta2509@...> <mailto:nikitagupta2509@... <mailto:nikitagupta2509@...>>> wrote: > > > > Hello Alexander > > > > I am not getting your query . Can u please explain your question? > > > > Regards > > Nikita Gupta > > > > On Wed, Jan 25, 2023, 18:35 Alexander Kanavin <alex.kanavin@... <mailto:alex.kanavin@...> <mailto:alex.kanavin@... <mailto:alex.kanavin@...>>> wrote: > >> > >> What happens if you bitbake libimx… thingy directly? > >> > >> Alex > >> > >> On Wed 25. Jan 2023 at 13.47, Nikita Gupta <nikitagupta2509@... <mailto:nikitagupta2509@...> <mailto:nikitagupta2509@... <mailto:nikitagupta2509@...>>> wrote: > >>> > >>> Hello list, > >>> > >>> I was just making image for imx8mplus by adding few pkgs in my local.conf but encountered few errors so i am here > for your help. > >>> I added below pkgs in my local.conf file > >>> > >>> IMAGE_INSTALL:append = "gstreamer1.0 gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-bad > gstreamer1.0-plugins-ugly gstreamer1.0-libav imx-vpuwrap imx-gpu-g2d imx-gpu-viv gstreamer1.0-plugins-imx > imx-gst1.0-plugin" > >>> LICENSE_FLAGS_WHITELIST = "commercial" > >>> IMAGE_INSTALL:append = "kernel-devsrc" > >>> IMAGE_INSTALL_append += "gstreamer1.0-rtsp-server gst-variable-rtsp-server" > >>> IMAGE_INSTALL:append = " gtk+3" > >>> CORE_IMAGE_EXTRA_INSTALL += " opencv libopencv-core-dev libopencv-highgui-dev libopencv-imgproc-dev > libopencv-objdetect-dev libopencv-ml-dev" > >>> IMAGE_ROOTFS_EXTRA_SPACE = "1048576 " > >>> > >>> So my local.conf file now looks like this > >>> So i am getting below error after baking my recipe ( Attached image). > >>> > >>> Please tell what should I need to do to resolve this. > >>> > >>> Thanks in advance > >>> > >>> > >>> > > > > >
-- Takayasu Ito Solution Department, Lineo Solutions, Inc. https://www.lineo.co.jp/english/ <https://www.lineo.co.jp/english/> Email: ito@... <mailto:ito@...> Yocto Project Ambassador
-- Takayasu Ito Yocto Project Ambassador Solution Department Lineo Solutions, Inc. https://www.lineo.co.jp/english/ Email: ito@...
|
|