|
Yocto Project Status WW06`22
Stephen Jolley
Current Dev Position: YP 3.5 M3 Next Deadline: 21th Feb. 2022 YP 3.5 M3 build
Next Team Meetings:
Key Status/Updates:
Everyone can now sign up for an account on the new system. Patchwork project maintainers please email mhalstead@... to have your access restored.
In particular, we’re struggling to understand the intermittent network issue with external hosts we’re seeing very occasionally.
Ways to contribute:
YP 3.5 Milestone Dates:
Upcoming dot releases:
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@...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
run.do_compile error on poky-dunfell release
Sourabh Hegde
Hello All,
When I am bitbaking my custom image for STM32MP1 based Avenger96 board I am facing some errors related to "analyze.l:466:19: error: format not a string literal and no format arguments [-Werror=format-security]". I don't understand why I am getting this error as this is the first I am facing it. Please find the below complete log: DEBUG: Executing python function autotools_aclocals DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common'] DEBUG: Python function autotools_aclocals finished DEBUG: Executing shell function do_compile NOTE: make -j 8 make all-recursive make[1]: Entering directory '/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0/build' Making all in src make[2]: Entering directory '/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0/build/src' Making all in libcommon make[3]: Entering directory '/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0/build/src/libcommon' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0/build/src/libcommon' Making all in libkbdfile make[3]: Entering directory '/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0/build/src/libkbdfile' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0/build/src/libkbdfile' Making all in libkeymap make[3]: Entering directory '/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0/build/src/libkeymap' make all-am make[4]: Entering directory '/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0/build/src/libkeymap' ../../arm-poky-linux-gnueabi-libtool --tag=CC --mode=compile arm-poky-linux-gnueabi-gcc -mthumb -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 -fstack-protector-strong -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0/recipe-sysroot -DHAVE_CONFIG_H -I. -I../../../kbd-2.2.0/src/libkeymap -I../.. -I../../../kbd-2.2.0/src/libkeymap -I. -I../../../kbd-2.2.0/src/libkeymap/.. -I./.. -I../../../kbd-2.2.0/src/libkeymap/../libcommon -I./../libcommon -I../../../kbd-2.2.0/src/libkeymap/../libkbdfile -I./../libkbdfile -DDATADIR=\"/usr/share\" -DLOCALEDIR=\"/usr/share/locale\" -U_GNU_SOURCE -funit-at-a-time -g -O2 -D_FORTIFY_SOURCE=2 -O2 -pipe -g -feliminate-unused-debug-types -fmacro-prefix-map=/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0=/usr/src/debug/kbd/2.2.0-r0 -fdebug-prefix-map=/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0=/usr/src/debug/kbd/2.2.0-r0 -fdebug-prefix-map=/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0/recipe-sysroot= -fdebug-prefix-map=/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0/recipe-sysroot-native= -Waggregate-return -Wall -Wcast-align -Wconversion -Wdisabled-optimization -Wextra -Wmissing-declarations -Wmissing-format-attribute -Wmissing-noreturn -Wmissing-prototypes -Wpointer-arith -Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings -c -o analyze.lo ../../../kbd-2.2.0/src/libkeymap/analyze.c arm-poky-linux-gnueabi-libtool: compile: arm-poky-linux-gnueabi-gcc -mthumb -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 -fstack-protector-strong -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0/recipe-sysroot -DHAVE_CONFIG_H -I. -I../../../kbd-2.2.0/src/libkeymap -I../.. -I../../../kbd-2.2.0/src/libkeymap -I. -I../../../kbd-2.2.0/src/libkeymap/.. -I./.. -I../../../kbd-2.2.0/src/libkeymap/../libcommon -I./../libcommon -I../../../kbd-2.2.0/src/libkeymap/../libkbdfile -I./../libkbdfile -DDATADIR=\"/usr/share\" -DLOCALEDIR=\"/usr/share/locale\" -U_GNU_SOURCE -funit-at-a-time -g -O2 -D_FORTIFY_SOURCE=2 -O2 -pipe -g -feliminate-unused-debug-types -fmacro-prefix-map=/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0=/usr/src/debug/kbd/2.2.0-r0 -fdebug-prefix-map=/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0=/usr/src/debug/kbd/2.2.0-r0 -fdebug-prefix-map=/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0/recipe-sysroot= -fdebug-prefix-map=/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0/recipe-sysroot-native= -Waggregate-return -Wall -Wcast-align -Wconversion -Wdisabled-optimization -Wextra -Wmissing-declarations -Wmissing-format-attribute -Wmissing-noreturn -Wmissing-prototypes -Wpointer-arith -Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings -c ../../../kbd-2.2.0/src/libkeymap/analyze.c -fPIC -DPIC -o .libs/analyze.o analyze.l: In function 'find_incl_file_near_fn': analyze.l:141:24: warning: passing argument 2 of 'kbdfile_find' from incompatible pointer type [-Wincompatible-pointer-types] In file included from ../../../kbd-2.2.0/src/libkeymap/keymap/kmap.h:36, from ../../../kbd-2.2.0/src/libkeymap/keymap.h:8, from ../../../kbd-2.2.0/src/libkeymap/analyze.c:1: ../../../kbd-2.2.0/src/libkeymap/../libkbdfile/kbdfile.h:40:37: note: expected 'char **' but argument is of type 'const char **' 40 | int kbdfile_find(char *fnam, char **dirpath, char **suffixes, struct kbdfile *fp); | ~~~~~~~^~~~~~~ analyze.l:141:42: warning: passing argument 3 of 'kbdfile_find' from incompatible pointer type [-Wincompatible-pointer-types] In file included from ../../../kbd-2.2.0/src/libkeymap/keymap/kmap.h:36, from ../../../kbd-2.2.0/src/libkeymap/keymap.h:8, from ../../../kbd-2.2.0/src/libkeymap/analyze.c:1: ../../../kbd-2.2.0/src/libkeymap/../libkbdfile/kbdfile.h:40:53: note: expected 'char **' but argument is of type 'const char * const*' 40 | int kbdfile_find(char *fnam, char **dirpath, char **suffixes, struct kbdfile *fp); | ~~~~~~~^~~~~~~~ analyze.l: In function 'find_standard_incl_file': analyze.l:168:22: warning: passing argument 2 of 'kbdfile_find' from incompatible pointer type [-Wincompatible-pointer-types] In file included from ../../../kbd-2.2.0/src/libkeymap/keymap/kmap.h:36, from ../../../kbd-2.2.0/src/libkeymap/keymap.h:8, from ../../../kbd-2.2.0/src/libkeymap/analyze.c:1: ../../../kbd-2.2.0/src/libkeymap/../libkbdfile/kbdfile.h:40:37: note: expected 'char **' but argument is of type 'const char * const*' 40 | int kbdfile_find(char *fnam, char **dirpath, char **suffixes, struct kbdfile *fp); | ~~~~~~~^~~~~~~ analyze.l:168:40: warning: passing argument 3 of 'kbdfile_find' from incompatible pointer type [-Wincompatible-pointer-types] In file included from ../../../kbd-2.2.0/src/libkeymap/keymap/kmap.h:36, from ../../../kbd-2.2.0/src/libkeymap/keymap.h:8, from ../../../kbd-2.2.0/src/libkeymap/analyze.c:1: ../../../kbd-2.2.0/src/libkeymap/../libkbdfile/kbdfile.h:40:53: note: expected 'char **' but argument is of type 'const char * const*' 40 | int kbdfile_find(char *fnam, char **dirpath, char **suffixes, struct kbdfile *fp); | ~~~~~~~^~~~~~~~ analyze.l:197:24: warning: passing argument 2 of 'kbdfile_find' from incompatible pointer type [-Wincompatible-pointer-types] In file included from ../../../kbd-2.2.0/src/libkeymap/keymap/kmap.h:36, from ../../../kbd-2.2.0/src/libkeymap/keymap.h:8, from ../../../kbd-2.2.0/src/libkeymap/analyze.c:1: ../../../kbd-2.2.0/src/libkeymap/../libkbdfile/kbdfile.h:40:37: note: expected 'char **' but argument is of type 'const char * const*' 40 | int kbdfile_find(char *fnam, char **dirpath, char **suffixes, struct kbdfile *fp); | ~~~~~~~^~~~~~~ analyze.l:197:42: warning: passing argument 3 of 'kbdfile_find' from incompatible pointer type [-Wincompatible-pointer-types] In file included from ../../../kbd-2.2.0/src/libkeymap/keymap/kmap.h:36, from ../../../kbd-2.2.0/src/libkeymap/keymap.h:8, from ../../../kbd-2.2.0/src/libkeymap/analyze.c:1: ../../../kbd-2.2.0/src/libkeymap/../libkbdfile/kbdfile.h:40:53: note: expected 'char **' but argument is of type 'const char * const*' 40 | int kbdfile_find(char *fnam, char **dirpath, char **suffixes, struct kbdfile *fp); | ~~~~~~~^~~~~~~~ analyze.l: In function 'find_incl_file': analyze.l:210:27: warning: passing argument 2 of 'kbdfile_find' from incompatible pointer type [-Wincompatible-pointer-types] In file included from ../../../kbd-2.2.0/src/libkeymap/keymap/kmap.h:36, from ../../../kbd-2.2.0/src/libkeymap/keymap.h:8, from ../../../kbd-2.2.0/src/libkeymap/analyze.c:1: ../../../kbd-2.2.0/src/libkeymap/../libkbdfile/kbdfile.h:40:37: note: expected 'char **' but argument is of type 'const char * const*' 40 | int kbdfile_find(char *fnam, char **dirpath, char **suffixes, struct kbdfile *fp); | ~~~~~~~^~~~~~~ analyze.l:210:45: warning: passing argument 3 of 'kbdfile_find' from incompatible pointer type [-Wincompatible-pointer-types] In file included from ../../../kbd-2.2.0/src/libkeymap/keymap/kmap.h:36, from ../../../kbd-2.2.0/src/libkeymap/keymap.h:8, from ../../../kbd-2.2.0/src/libkeymap/analyze.c:1: ../../../kbd-2.2.0/src/libkeymap/../libkbdfile/kbdfile.h:40:53: note: expected 'char **' but argument is of type 'const char * const*' 40 | int kbdfile_find(char *fnam, char **dirpath, char **suffixes, struct kbdfile *fp); | ~~~~~~~^~~~~~~~ analyze.l:225:26: warning: passing argument 2 of 'kbdfile_find' from incompatible pointer type [-Wincompatible-pointer-types] In file included from ../../../kbd-2.2.0/src/libkeymap/keymap/kmap.h:36, from ../../../kbd-2.2.0/src/libkeymap/keymap.h:8, from ../../../kbd-2.2.0/src/libkeymap/analyze.c:1: ../../../kbd-2.2.0/src/libkeymap/../libkbdfile/kbdfile.h:40:37: note: expected 'char **' but argument is of type 'const char **' 40 | int kbdfile_find(char *fnam, char **dirpath, char **suffixes, struct kbdfile *fp); | ~~~~~~~^~~~~~~ analyze.l:225:36: warning: passing argument 3 of 'kbdfile_find' from incompatible pointer type [-Wincompatible-pointer-types] In file included from ../../../kbd-2.2.0/src/libkeymap/keymap/kmap.h:36, from ../../../kbd-2.2.0/src/libkeymap/keymap.h:8, from ../../../kbd-2.2.0/src/libkeymap/analyze.c:1: ../../../kbd-2.2.0/src/libkeymap/../libkbdfile/kbdfile.h:40:53: note: expected 'char **' but argument is of type 'const char * const*' 40 | int kbdfile_find(char *fnam, char **dirpath, char **suffixes, struct kbdfile *fp); | ~~~~~~~^~~~~~~~ In file included from analyze.l:10: analyze.l: In function 'yylex': analyze.l:466:19: error: format not a string literal and no format arguments [-Werror=format-security] ../../../kbd-2.2.0/src/libkeymap/contextP.h:79:55: note: in definition of macro 'lk_log_cond' 79 | lk_log(ctx, level, __FILE__, __LINE__, __func__, ##arg); \ | ^~~ analyze.l:466:6: note: in expansion of macro 'ERR' cc1: some warnings being treated as errors make[4]: *** [Makefile:604: analyze.lo] Error 1 make[4]: Leaving directory '/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0/build/src/libkeymap' make[3]: *** [Makefile:476: all] Error 2 make[3]: Leaving directory '/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0/build/src/libkeymap' make[2]: *** [Makefile:1083: all-recursive] Error 1 make[2]: Leaving directory '/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0/build/src' make[1]: *** [Makefile:471: all-recursive] Error 1 make[1]: Leaving directory '/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0/build' ERROR: oe_runmake failed make: *** [Makefile:402: all] Error 2 WARNING: exit code 1 from a shell command. ERROR: Execution of '/root/build-swu-v2/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/kbd/2.2.0-r0/temp/run.do_compile.380' failed with exit code 1 Can anyone please let me know how to fix this issue? Your help will be much appreciated. Thanks in advance.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: [meta-anaconda][PATCH] Update SRC_URI git default branch
kai
On 1/21/22 2:10 PM, Changqing Li wrote:
From: Changqing Li <changqing.li@...> Signed-off-by: Changqing Li <changqing.li@...> Merged. Thanks, --- recipes-installer/python3-dasbus/python3-dasbus_1.6.bb | 2 +- recipes-installer/python3-productmd/python3-productmd_1.21.bb | 2 +- recipes-installer/python3-simpleline/python3-simpleline_1.3.bb | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/recipes-installer/python3-dasbus/python3-dasbus_1.6.bb b/recipes-installer/python3-dasbus/python3-dasbus_1.6.bb index c42ab52..5b87391 100644 --- a/recipes-installer/python3-dasbus/python3-dasbus_1.6.bb +++ b/recipes-installer/python3-dasbus/python3-dasbus_1.6.bb @@ -4,7 +4,7 @@ SECTION = "devel" LICENSE = "LGPLv2.1" LIC_FILES_CHKSUM = "file://LICENSE;md5=1803fa9c2c3ce8cb06b4861d75310742" -SRC_URI = "git://github.com/rhinstaller/dasbus.git;protocol=https;" +SRC_URI = "git://github.com/rhinstaller/dasbus.git;protocol=https;branch=master" SRCREV = "63b22fe4a7b2f98739279b2a4c6107eebd8d5a58" S = "${WORKDIR}/git" diff --git a/recipes-installer/python3-productmd/python3-productmd_1.21.bb b/recipes-installer/python3-productmd/python3-productmd_1.21.bb index 98fd0de..8dcd434 100644 --- a/recipes-installer/python3-productmd/python3-productmd_1.21.bb +++ b/recipes-installer/python3-productmd/python3-productmd_1.21.bb @@ -6,7 +6,7 @@ SECTION = "devel" LICENSE = "LGPLv2.1" LIC_FILES_CHKSUM = "file://LICENSE;md5=768997ba510a952bef1775c50bc22b00" -SRC_URI = "git://github.com/release-engineering/productmd;protocol=https; \ +SRC_URI = "git://github.com/release-engineering/productmd;protocol=https;branch=master \ file://add-wrlinux-version-pattern.patch \ " SRCREV = "a8268944c8a6064697ccb4d24e52dc666ab03ed4" diff --git a/recipes-installer/python3-simpleline/python3-simpleline_1.3.bb b/recipes-installer/python3-simpleline/python3-simpleline_1.3.bb index dcf7e1d..651b9d0 100644 --- a/recipes-installer/python3-simpleline/python3-simpleline_1.3.bb +++ b/recipes-installer/python3-simpleline/python3-simpleline_1.3.bb @@ -6,7 +6,7 @@ SECTION = "devel" LICENSE = "GPLv2" LIC_FILES_CHKSUM = "file://COPYING;md5=5f4f48e95324081879552f19cd16c54a" -SRC_URI = "git://github.com/rhinstaller/python-simpleline;protocol=https;" +SRC_URI = "git://github.com/rhinstaller/python-simpleline;protocol=https;branch=master" SRCREV = "1c21ffdeda9eed27e5ad8ec16aee467f8daecd50" S = "${WORKDIR}/git" inherit setuptools3
-- Kai Kang Wind River Linux
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
M+ & H bugs with Milestone Movements WW06
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Enhancements/Bugs closed WW06!
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Current high bug count owners for Yocto Project 3.5
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Yocto Project Newcomer & Unassigned Bugs - Help Needed
Stephen Jolley
All,
The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading: https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project. If anyone can help, please take ownership of the bug and send patches! If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.
Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 400 unassigned or newcomer bugs.
We're hoping people may be able to spare some time now and again to help out with these. Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system. There are also roughly four different "priority" classes right now, “3.5, “3.6”, "3.99" and "Future", the more pressing/urgent issues being in "3.4" and then “3.5”.
Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account). The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: patching files under "dynamic-layers"
Monsees, Steven C (US)
Never mind was able to work this out…
From: yocto@... <yocto@...>
On Behalf Of Monsees, Steven C (US) via lists.yoctoproject.org
Sent: Monday, February 7, 2022 10:42 AM To: yocto@... Subject: [yocto] patching files under "dynamic-layers"
I am building with zeus 3.0.4, Intel based…
I trying to learn how to introduce a patch to files brought in by packages under “dynamic –layers”… my bbappend appears not to be applying my test patch (even though no errors/warnings thrown)…
This is the package I am trying to manipulate:
/disk0/scratch/smonsees/yocto/workspace_3/meta-intel/dynamic-layers/clang-layer/recipes-opencl/igc It contains: files intel-graphics-compiler_1.0.11.bb
This is my recipe to apply patch:
/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/meta-intel/dynamic-layers/clang-layer/recipes-opencl/igc It contains: files intel-graphics-compiler_1.0.11.bbappend
files - contains the file I am attempting to patch (FILE_TO_PATCH.patch) intel-graphics-compiler_1.0.11.bbappend is setup like so, where
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
SRC_URI += "\ "
I attempted to male use of BBFILES_DYNAMIC but even though I get no error, patch is not applied.
conf/layer.conf: BBFILES_DYNAMIC += " \ clang-layer:$(LAYERDIR)/dynamic-layers/clang-layer/recipes-opencl/igc/*.bbappend \ "
Can you explain to me the proper way to patch files under these circumstances and where I went wrong ?
Thanks, Steve
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: ERROR: could not relocate installing toolchain SDK
Add Denis since he may have missed
Sundeep's email.
On 2022-02-04 01:52, Sundeep KOKKONDA
wrote:
Hello, The 4096 comes from PATH_MAX:
-- # Randy MacLeod # Wind River Linux
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
patching files under "dynamic-layers"
Monsees, Steven C (US)
I am building with zeus 3.0.4, Intel based…
I trying to learn how to introduce a patch to files brought in by packages under “dynamic –layers”… my bbappend appears not to be applying my test patch (even though no errors/warnings thrown)…
This is the package I am trying to manipulate:
/disk0/scratch/smonsees/yocto/workspace_3/meta-intel/dynamic-layers/clang-layer/recipes-opencl/igc It contains: files intel-graphics-compiler_1.0.11.bb
This is my recipe to apply patch:
/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/meta-intel/dynamic-layers/clang-layer/recipes-opencl/igc It contains: files intel-graphics-compiler_1.0.11.bbappend
files - contains the file I am attempting to patch (FILE_TO_PATCH.patch) intel-graphics-compiler_1.0.11.bbappend is setup like so, where
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
SRC_URI += "\ file://FILE_TO_PATCH.patch \ "
I attempted to male use of BBFILES_DYNAMIC but even though I get no error, patch is not applied.
conf/layer.conf: BBFILES_DYNAMIC += " \ clang-layer:$(LAYERDIR)/dynamic-layers/clang-layer/recipes-opencl/igc/*.bbappend \ "
Can you explain to me the proper way to patch files under these circumstances and where I went wrong ?
Thanks, Steve
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: gpsd autostart with systemd?
Matthias Klein
Hello Jose,
You need to add the systemd service, the socket service is already there.Thank you very much for your help! Best regards, Matthias
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: gpsd autostart with systemd?
Jose Quaresma
Hi Matthias, You need to add the systemd service, the socket service is already there. SYSTEMD_SERVICE:${PN} += "${BPN}.service" Matthias Klein <matthias.klein@...> escreveu no dia segunda, 7/02/2022 à(s) 08:19:
Hello, --
Best regards, José Quaresma
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
gpsd autostart with systemd?
Matthias Klein
Hello,
what needs to be in a bbapped so that gpsd is started automatically at boot time, and not only when the first accesses the gpsd socket? http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-navigation/gpsd/gpsd_3.23.1.bb Best regards, Matthias
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: readonly rootfs - storing data in separate partition
tomzy
Hi Not long ago we use it in couple of projects. Main repo can be found You can also find our fork with couple of changes (on of them is for example
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: readonly rootfs - storing data in separate partition
rootfs-overlay is the perfect solution for your case.
-- Marco Cavallini | KOAN sas Bergamo - Italia embedded software engineering https://KoanSoftware.com
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: readonly-rootfs-overlay
Matthias Klein
Hello Howard,
i use parts of it (without a writeable partition, just a tmpfs) in a separate layer: https://github.com/matthiasklein/meta-distro-coffee/blob/master/recipes-core/readonly-rootfs-overlay/readonly-rootfs-overlay_1.0.bb Best regards, Von: yocto@... <yocto@...>
Im Auftrag von Howard via lists.yoctoproject.org
Hi:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: readonly rootfs - storing data in separate partition
Howard
Hi:
I was wondering if anybody is using meta-readonly-rootfs-overlay? Thanks Howard
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Resistive touchscreen calibration for libinput
Steve Sakoman
On Sat, Feb 5, 2022 at 4:05 AM Electronic Consult
<electronicconsult1@gmail.com> wrote: Since you are using tslib, the ts_calibrate utility would be the obvious choice. Include the tslib_calibrate package in your image. You might also find the tslib_tests package useful. Steve
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
[meta-selinux][PATCH] prelink: drop bbappend
Tim Orling
prelink has been dropped from oe-core [1], so the bbappend can no longer be
applied. [1] https://git.openembedded.org/openembedded-core/commit/?id=23c0be78106f1d1e2bb9c724174a1bb8c56c2469 Signed-off-by: Tim Orling <tim.orling@konsulko.com> --- recipes-devtools/prelink/prelink_git.bbappend | 1 - 1 file changed, 1 deletion(-) delete mode 100644 recipes-devtools/prelink/prelink_git.bbappend diff --git a/recipes-devtools/prelink/prelink_git.bbappend b/recipes-devtools/prelink/prelink_git.bbappend deleted file mode 100644 index 74e22b3..0000000 --- a/recipes-devtools/prelink/prelink_git.bbappend +++ /dev/null @@ -1 +0,0 @@ -inherit ${@bb.utils.contains('DISTRO_FEATURES', 'selinux', 'enable-selinux', '', d)} -- 2.25.1
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Resistive touchscreen calibration for libinput
Electronic Consult <electronicconsult1@...>
Hello all, Apologies if this is the incorrect group to post to, I haven't posted previously. I'm working with an Atmel/ Microchip SAMA5D4
Xplained board & a resistive touchscreen. I'm using a GUI framework
that has issues dealing with evdev & tslib so looks like I need to
find a screen calibration method for libinput, which the GUI framework
favours. Can anyone please suggest a solution for this? I've taken a look at a recipe for xinput-calibrator & it seems like a possible solution. However my build isn't running a desktop GUI so not sure if this is a proper fit. I'd appreciate if anyone could point me in the right direction. Many thanks, Owen
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|