Re: [meta-raspberrypi][PATCH] userland: add knob for ALL_APPS
Hi Trevor
On Fri, Nov 27, 2020 at 2:17 AM Trevor Woerner <twoerner@...> wrote: change is okay, Can you create a GH pull request for this please Signed-off-by: Trevor Woerner <twoerner@...>
|
|
patch apply for .bb file
NIKHIL PATIL <nikhilvp29@...>
Hi team , We are tring to apply to patch to default .bb file. means in gpsd_3.17.bb file we did some changes but after taking patch we are not able to apply it . steps followd :- 1) git status 2) git diff yocto_build/meta-openembedded/meta-oe/recipes-navigation/gpsd/gpsd_3.17.bb > 0001_add_line_in_gpsd.patch 3) git checkout yocto_build/meta-openembedded/meta-oe/recipes-navigation/gpsd/gpsd_3.17.bb after these i applied gpsd patch in /yocto_build/meta-intel-leafhill/recipes-kernel/linux/linux-intel/leafhill.scc file but after appling getting following errors . ERRORS :- [INFO]: Context reduced git-am of .kernel-meta//patches//patches/0001_add_line_in_gpsd.patch with "git am" did not work, trying "apply". | error: yocto_build/meta-openembedded/meta-oe/recipes-navigation/gpsd/gpsd_3.17.bb: does not exist in index| [ERROR]: Application of .kernel-meta//patches//patches/0001_add_line_in_gpsd.patch failed. | Patch needs to be refreshed. Sample resolution script: | .git/rebase-apply/resolve_rejects | ERROR: Could not apply patches for intel-corei7-64. | ERROR: Patch failures can be resolved in the linux source directory /data/nikhil/inti_dmsv/yocto_build/build/tmp/work-shared/intel-corei7-64/kernel-source) douts :- 1) Can we apply a patch to default code means (files in meta or files( .bb ) in meta-intel folder, etc) ? because we are able to apply a patch for kernel code (driver file ) , but for .bb file patch appling we are facing issue . 2) how to apply a patch to default .bb file in meta layers ? can u please tell procedure . thanks in advance .
|
|
[meta-raspberrypi][PATCH] userland: add knob for ALL_APPS
Trevor Woerner
The userland sources include a bunch of sample applications. Add an "allapps"
PACKAGECONFIG to allow the user to build the additional optional applications. Signed-off-by: Trevor Woerner <twoerner@...> --- ...cations-remove-non-existent-projects.patch | 30 +++++++++++++++++++ ...ptionally-build-wayland-specific-app.patch | 28 +++++++++++++++++ recipes-graphics/userland/userland_git.bb | 4 +++ 3 files changed, 62 insertions(+) create mode 100644 recipes-graphics/userland/files/0022-all-host_applications-remove-non-existent-projects.patch create mode 100644 recipes-graphics/userland/files/0023-hello_pi-optionally-build-wayland-specific-app.patch diff --git a/recipes-graphics/userland/files/0022-all-host_applications-remove-non-existent-projects.patch b/recipes-graphics/userland/files/0022-all-host_applications-remove-non-existent-projects.patch new file mode 100644 index 0000000..595eefb --- /dev/null +++ b/recipes-graphics/userland/files/0022-all-host_applications-remove-non-existent-projects.patch @@ -0,0 +1,30 @@ +From 451e8458e45926e4e1c0433864ac4cf8b05d792b Mon Sep 17 00:00:00 2001 +From: Trevor Woerner <twoerner@...> +Date: Fri, 27 Nov 2020 03:12:26 -0500 +Subject: [PATCH] all host_applications: remove non-existent projects + +The ALL_APPS symbol will optionally build an additional set of projects, +however, several of them don't exist anymore. Remove them from the list of +ALL_APPS. + +Upstream-status: submitted [https://github.com/raspberrypi/userland/pull/661] +Signed-off-by: Trevor Woerner <twoerner@...> +--- + host_applications/linux/CMakeLists.txt | 4 ---- + 1 file changed, 4 deletions(-) + +diff --git a/host_applications/linux/CMakeLists.txt b/host_applications/linux/CMakeLists.txt +index 928b637..554ae46 100644 +--- a/host_applications/linux/CMakeLists.txt ++++ b/host_applications/linux/CMakeLists.txt +@@ -14,10 +14,6 @@ add_subdirectory(apps/dtoverlay) + add_subdirectory(apps/dtmerge) + + if(ALL_APPS) +- add_subdirectory(apps/vcdbg) +- add_subdirectory(libs/elftoolchain) +- # add_subdirectory(apps/smct) +- add_subdirectory(apps/edid_parser) + add_subdirectory(apps/hello_pi) + endif() + diff --git a/recipes-graphics/userland/files/0023-hello_pi-optionally-build-wayland-specific-app.patch b/recipes-graphics/userland/files/0023-hello_pi-optionally-build-wayland-specific-app.patch new file mode 100644 index 0000000..642ee86 --- /dev/null +++ b/recipes-graphics/userland/files/0023-hello_pi-optionally-build-wayland-specific-app.patch @@ -0,0 +1,28 @@ +From 5f4324a0008c2e8e1f511432f98bf85c9fffd35c Mon Sep 17 00:00:00 2001 +From: Trevor Woerner <twoerner@...> +Date: Fri, 27 Nov 2020 03:18:50 -0500 +Subject: [PATCH] hello_pi: optionally build wayland-specific app + +Only build the wayland-specific hello_pi app when building for wayland. + +Upstream-status: inappropriate [the wayland example is not part of upstream] +Signed-off-by: Trevor Woerner <twoerner@...> +--- + host_applications/linux/apps/hello_pi/CMakeLists.txt | 4 +++- + 1 file changed, 3 insertions(+), 1 deletion(-) + +diff --git a/host_applications/linux/apps/hello_pi/CMakeLists.txt b/host_applications/linux/apps/hello_pi/CMakeLists.txt +index 2849fad..7de3265 100644 +--- a/host_applications/linux/apps/hello_pi/CMakeLists.txt ++++ b/host_applications/linux/apps/hello_pi/CMakeLists.txt +@@ -25,7 +25,9 @@ add_subdirectory(hello_encode) + add_subdirectory(hello_jpeg) + add_subdirectory(hello_videocube) + add_subdirectory(hello_teapot) +-add_subdirectory(hello_wayland) ++if (BUILD_WAYLAND) ++ add_subdirectory(hello_wayland) ++endif() + + if(BUILD_FONT) + set(VGFONT_SRCS libs/vgfont/font.c libs/vgfont/vgft.c libs/vgfont/graphics.c) diff --git a/recipes-graphics/userland/userland_git.bb b/recipes-graphics/userland/userland_git.bb index 1d9dc1e..32aa4a5 100644 --- a/recipes-graphics/userland/userland_git.bb +++ b/recipes-graphics/userland/userland_git.bb @@ -42,6 +42,8 @@ SRC_URI = "\ file://0019-libfdt-Undefine-__wordsize-if-already-defined.patch \ file://0020-openmaxil-add-pkg-config-file.patch \ file://0021-cmake-Disable-format-overflow-warning-as-error.patch \ + file://0022-all-host_applications-remove-non-existent-projects.patch \ + file://0023-hello_pi-optionally-build-wayland-specific-app.patch \ " SRC_URI_remove_toolchain-clang = "file://0021-cmake-Disable-format-overflow-warning-as-error.patch" @@ -52,8 +54,10 @@ inherit cmake pkgconfig ASNEEDED = "" +ALLAPPS = "${@bb.utils.contains('PACKAGECONFIG', 'allapps', '-DALL_APPS=true', '', d)}" EXTRA_OECMAKE = "-DCMAKE_BUILD_TYPE=Release -DCMAKE_EXE_LINKER_FLAGS='-Wl,--no-as-needed' \ -DVMCS_INSTALL_PREFIX=${exec_prefix} \ + ${ALLAPPS} \ " EXTRA_OECMAKE_append_aarch64 = " -DARM64=ON " -- 2.28.0.497.g54e85e7af1
|
|
Re: Yocto AWS MQTT: ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1108)
#python
Diego Santa Cruz
Hi there,
From: yocto@... <yocto@...> On Behalf Of vijayrakeshmunganda via lists.yoctoproject.org
Sent: 27 November 2020 09:47 To: yocto@... Subject: [yocto] Yocto AWS MQTT: ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1108) #python Hi,
I'm new to Yocto project. I'm running basic MQTT publish code in python, when I run my code I got error as, "ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1108)". I had downloaded activated certificates from AWS, but I don't why I'm getting this error. I'm I missing any package or anything? Please help me in this regard, thank you. Thanks & Regards,
VR The “certificate is not yet valid” message makes me think that you may have a date in the past in your system, check the date and time with “date” to do proper certificate
validation you need to make arrangements to have the date and time on your target set properly, either you can trust the RTC to have the correct time or you need something like ntp.
Best,
Diego
--
Diego Santa Cruz, PhD Technology Architect spinetix.com
|
|
Yocto AWS MQTT: ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1108)
#python
Vijay Rakesh Munganda
Hi,
I'm new to Yocto project. I'm running basic MQTT publish code in python, when I run my code I got error as, "ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1108)". I had downloaded activated certificates from AWS, but I don't why I'm getting this error. I'm I missing any package or anything? Please help me in this regard, thank you. Thanks & Regards, VR
|
|
Re: multilib: lib32-libgdiplus complaining about qemuwrapper
Pelle Windestam
I am using Yocto 2.5 and have a working multilib-enabled image based on poky which includes libgdiplus (64-bit). Due to requirements I had to add the 32-bit version, so I added lib32-libgdiplus to my image recipe. This caused the following error output from bitbake: WARNING: tmlinux-image-1.0-r0 do_rootfs: The postinstall intercept hook 'update_gio_module_cache-lib32' failed, details in /home/pelle/development/var-fsl-yocto/build_kodkod/tmp/work/imx8qxpb0_var_som-poky-linux/tmlinux-image/1.0-r0/temp/log.do_rootfs While searching for the root cause of this, I discovered a change to update_gio_module_cache (https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/scripts/postinst-intercepts/update_gio_module_cache?id=87631af64032b18ea354b27cc586ec13391bd143) that I thought might help. I applied this change (and the changes from https://github.com/openembedded/openembedded-core/commit/d10fd6ae3fe46290c6e3a5250878966d9f12ca3f for the qemuwrapper-cross_1.0.bb recipe) to my local code, and once again tried building the image. The error message from bitbake is the same, but in the do_rootfs log I find this: /home/pelle/development/var-fsl-yocto/build_kodkod/tmp/work/imx8qxpb0_var_som-poky-linux/tmlinux-image/1.0-r0/intercept_scripts-bd1c31820bf736a004f4ebe71461d6fa3ae23f7d97783c8f28a606e086741d8a/update_gio_module_cache-lib32: 15: /home/pelle/development/var-fsl-yocto/build_kodkod/tmp/work/imx8qxpb0_var_som-poky-linux/tmlinux-image/1.0-r0/intercept_scripts-bd1c31820bf736a004f4ebe71461d6fa3ae23f7d97783c8f28a606e086741d8a/update_gio_module_cache-lib32: lib32-qemuwrapper: not found If I search my tmp directory, there is nothing called "lib32-qemuwrapper", but there is "lib32-qemuwrapper-cross".Hi again, I have spent a few more hours digging into this and made some discoveries. The problem does not seem to be directly with libgdiplus, but with glib-2.0, which is responsible for calling the "update_gio_module_cache" script, which gets set up as a postinstall intercept script. The update_gio_module_cache script gets executed both for the regular libgdiplus (works fine), and for lib32-libgdiplus. The issue is with lib32-libgdiplus, because lib32-libgdiplus wants to run "lib32-qemuwrapper", but the location of lib32-qemuwrapper is not in the PATH when it runs the update_gio_module_cache-lib32 script (it seems like the incorrect sysroot is used). When looking at the output from bitbake -e for my image recipe, I can see that the variable that points out the location for the recipe-sysroot ($STAGING_DIR_HOST) directory gets correctly set up for the non-lib32 packages, but it uses the same variable content when running update_gio_module_cache-lib32. It seems to me like the do_rootfs task would have to do a second pass, with the recipe-sysroot set up correctly for multilib packages, to get this working. I am not familiar enough with bitbake to understand exactly how this should be resolved. My current "solution" is to modify the package_manager.py script to manually add the lib32-sysroot to the path before running intercept scripts (really ugly). Any pointers in the right direction would be much appreciated. //Pelle
|
|
Re: QA notification for completed autobuilder build (yocto-3.1.4.rc1)
Sangeeta Jain
Hi all,
toggle quoted messageShow quoted text
Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.4.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. Coffee Lake 3. NUC 7 4. NUC 6 5. Edgerouter 6. Beaglebone ETA for completion is next Tuesday, December 01. Thanks, Sangeeta
-----Original Message-----
|
|
Re: U-Boot sama5d3 xplained issue
Federico Pellegrin
Hi David, If you change it directly, changes may not be taken into account for the rebuild. And if the package build gets retriggered, then the whole repository is deleted (including your local changes), redownloaded, repatched and so on. So while it may by chance work by modifying locally in certain conditions, it will most likely not. I would see two ways: 1) Create a patch that does your changes and add it to the recipe (most likely now in a custom layer) as a patch 2) Fork the repository, add all your customizations there, and point the recipe (again most likely now in a custom layer) to that one. Cheers, F.
Il giorno ven 27 nov 2020 alle ore 01:35 David Novak <david.novak@...> ha scritto:
|
|
Re: U-Boot sama5d3 xplained issue
David Novak <david.novak@...>
We changed the file directly. Since it's a custom file, I don't think it is being downloaded. What is the easiest way to determine if it's being downloaded? Thanks,
On 11/23/2020 2:16 AM, Federico
Pellegrin wrote:
|
|
Re: How to Add Packages to Python3
Konrad Weihmann <kweihmann@...>
Just add RDEPENDS_${PN] += "python3-json" to the recipe that creates the package, that contains the mentioned python script.
toggle quoted messageShow quoted text
Alternatively add IMAGE_INSTALL += "python3-json" to the image the script is in. As this is a core module (shipped by python3) the mapping is purely based on the python3-manifest.json
On 26.11.20 12:22, vijayrakeshmunganda@... wrote:
Hi,
|
|
Re: [OE-core][PATCH v2] kernel-dummy: fix executing unexpected tasks
Andrej Valek <andrej.valek@...>
No problem, you can keep the deploy task dependency, like it was.
toggle quoted messageShow quoted text
Regards, Andrej
On Thu, 2020-11-26 at 14:44 +0000, Valek, Andrej wrote:No it's not a leftover. I've just copied it from kernel.bbclass, whereI'm trying to work out why we need the extra dependencies when the tasks are empty.
|
|
Re: [OE-core][PATCH v2] kernel-dummy: fix executing unexpected tasks
Richard Purdie
On Thu, 2020-11-26 at 14:44 +0000, Valek, Andrej wrote:
No it's not a leftover. I've just copied it from kernel.bbclass,I'm trying to work out why we need the extra dependencies when the tasks are empty. I can see how adding the inherit would help, I'm less sure how adding the deploy task after the others does though. Cheers, Richard
|
|
Re: [OE-core][PATCH v2] kernel-dummy: fix executing unexpected tasks
Andrej Valek <andrej.valek@...>
Hello Richard,
toggle quoted messageShow quoted text
No it's not a leftover. I've just copied it from kernel.bbclass, where this task is written correctly. But you can change it to previous version I guess. Regards, Andrej
On Wed, 2020-11-25 at 18:20 +0100, Andrej Valek wrote:- correctly save files into sstateIs this a leftover from the previous version of the patch? We don't normally need those constraints?
|
|
Re: [OE-core][PATCH v2] kernel-dummy: fix executing unexpected tasks
Richard Purdie
On Wed, 2020-11-25 at 18:20 +0100, Andrej Valek wrote:
- correctly save files into sstateIs this a leftover from the previous version of the patch? We don't normally need those constraints? Cheers, Richard
|
|
Re: Error during do_install for linux-libc-headers_5.8 recipe during 'bitbake core-image-minimal'
aloofbynature@...
Thanks for the quick response. I started out with a fresh clone of poky and only executed 2 commands:
1) 'source poky-yocto-3.2/oe-init-build-env' 2) in my build directory 'bitbake core-image-minimal' The output from the console is: aloof@LAPTOP-AQOIU06O:~/projects/yocto-test$ source poky-yocto-3.2/oe-init-build-env You had no conf/local.conf file. This configuration file has therefore been created for you with some default values. You may wish to edit it to, for example, select a different MACHINE (target hardware). See conf/local.conf for more information as common configuration options are commented. You had no conf/bblayers.conf file. This configuration file has therefore been created for you with some default values. To add additional metadata layers into your configuration please add entries to conf/bblayers.conf. The Yocto Project has extensive documentation about OE including a reference manual which can be found at: http://yoctoproject.org/documentation For more information about OpenEmbedded see their website: http://www.openembedded.org/ ### Shell environment set up for builds. ### You can now run 'bitbake <target>' Common targets are: core-image-minimal core-image-sato meta-toolchain meta-ide-support You can also run generated qemu images with a command like 'runqemu qemux86' Other commonly useful commands are: - 'devtool' and 'recipetool' handle common recipe tasks - 'bitbake-layers' handles common layer tasks - 'oe-pkgdata-util' handles common target package tasks aloof@LAPTOP-AQOIU06O:~/projects/yocto-test/build$ bitbake core-image-minimal WARNING: You are running bitbake under WSLv2, this works properly but you should optimize your VHDX file eventually to avoid running out of storage space Loading cache: 100% | | ETA: --:--:--Loaded 0 entries from dependency cache. Parsing recipes: 100% |##################################################################################| Time: 0:00:15Parsing of 784 .bb files complete (0 cached, 784 parsed). 1353 targets, 42 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.48.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "ubuntu-20.04" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "3.2" TUNE_FEATURES = "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "<unknown>:<unknown>" NOTE: Fetching uninative binary shim http://downloads.yoctoproject.org/releases/uninative/2.9/x86_64-nativesdk-libc.tar.xz;sha256sum=d07916b95c419c81541a19c8ef0ed8cbd78ae18437ff28a4c8a60ef40518e423 (will check PREMIRRORS first) Initialising tasks: 100% |###############################################################################| Time: 0:00:02Sstate summary: Wanted 1279 Found 0 Missed 1279 Current 0 (0% match, 0% complete) NOTE: Executing Tasks ERROR: Task (/home/aloof/projects/yocto-test/poky-yocto-3.2/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.8.bb:do_install) failed with exit code '134' NOTE: Tasks Summary: Attempted 793 tasks of which 0 didn't need to be rerun and 1 failed. Summary: 1 task failed: /home/aloof/projects/yocto-test/poky-yocto-3.2/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.8.bb:do_install Summary: There was 1 WARNING message shown. I'm not sure which log file. I'm attaching the one I found in the tmp directory. Is there a specific location you can point me to if this isn't the right log. Thanks, Ajay
|
|
Re: Error during do_install for linux-libc-headers_5.8 recipe during 'bitbake core-image-minimal'
Quentin Schulz
Hi,
On Thu, Nov 26, 2020 at 04:26:34AM -0800, aloofbynature@... wrote: Hello,To be able to help you we'd need the logs of this task. You can either paste the whole output on the console or send us the task log you can find if you carefully read the console output. Quentin
|
|
Re: Error during do_install for linux-libc-headers_5.8 recipe during 'bitbake core-image-minimal'
On Thu, 26 Nov 2020 at 12:26, <aloofbynature@...> wrote:
Could you share the command that you executed along with the full output that was printed? There's not really enough information here to diagnose the issue. Thanks, -- Paul Barker Konsulko Group
|
|
Error during do_install for linux-libc-headers_5.8 recipe during 'bitbake core-image-minimal'
aloofbynature@...
Hello,
I am just starting using Yocto Project and I've been following along with the getting started section of the mega manual. I am working on Ubuntu 20.04 LTS through WSL2 on Windows 10 (not sure if it matters but I'm running OS build 20231) trying to create an image using poky-yocto-3.2.
I've followed all setup steps and made sure the host has all necessary packages before cloning poky (I kept running into an error when trying to clone the repo because the connection was refused so I just extracted the poky-yocto-3.2 tarball). When I try to run 'bitbake core-image-minimal' I get an error saying the following task failed with exit code 134:
'poky-yocto-3.2/meta/recipes-
All the other recipes are installed with no problems.
The first time I tried this I changed local.conf in my build dir to build for qemuarm and next try I left everything as the default configuration but still got the same result. Any help fixing this issue is appreciated, thanks!
|
|
How to Add Packages to Python3
Vijay Rakesh Munganda
Hi,
I had installed a python file into the rootfs and when I tried to run, it throws an error as "ModuleNotFoundError: No module named 'json'". I tried to find bb file for jsonlib, but I couldn't find at https://layers.openembedded.org/layerindex/branch/master/recipes/?q=python+json. Also some sources suggest to add packages via python3-manifest.json. Kindly please help me in this regard. Thanks, VR
|
|
Re: Use of USERADD_PACKAGES with out recipe package files
On Thu, 26 Nov 2020 at 03:21, <andrew.loader@...> wrote:
You probably need to set `ALLOW_EMPTY_${PN}-user-sys`. See https://docs.yoctoproject.org/ref-manual/ref-variables.html?highlight=allow_empty#term-ALLOW_EMPTY. Thanks, -- Paul Barker Konsulko Group
|
|