Re: [yocto] [meta-rockchip][PATCH] trusted-firmware-a: Pin to use gcc for now
On Thu 2021-12-09 @ 05:14:58 PM, Khem Raj wrote: > tf-a built with clang is bloated for rk3399 SOCs with 2.6+ > it needs looking into, until then use gcc always to build it > > Signed-off-by: Khem Raj > Cc: Jon Mason > Cc: Ross Burton > --- > .../trusted-firmware-a/trusted-firmware-a_%.bbappend | 7 +++ > 1 file changed, 7 insertions(+) Applied to meta-rockchip master. Thanks! -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#55545): https://lists.yoctoproject.org/g/yocto/message/55545 Mute This Topic: https://lists.yoctoproject.org/mt/87627042/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] [OE-core] [PATCH] libva: move wayland PACKAGECONFIG to libva.inc
I encountered an error while trying to build libva under wayland. libva-initial
was missing wayland-native dependency and failed like this:
| Run-time dependency xfixes found: NO (tried pkgconfig and cmake)
| Run-time dependency wayland-client found: YES 1.19.0
| Program wayland-scanner /usr/bin/wayland-scanner found: NO
|
| ../libva-2.13.0/meson.build:107:4: ERROR: Program 'wayland-scanner
/usr/bin/wayland-scanner' not found
|
| A full log can be found at
/home/flk/build/poky/build-rock/tmp/work/cortexa72-cortexa53-crypto-poky-linux/libva-initial/2.13.0-r0/build/meson-logs/meson-log.txt
| ERROR: meson failed
| WARNING: exit code 1 from a shell command.
This commit moves the PACKAGECONFIG[wayland] to libva.inc to make it available
to libva-initial also
Signed-off-by: MarkusVolk
---
meta/recipes-graphics/libva/libva.inc | 7 +++
meta/recipes-graphics/libva/libva_2.13.0.bb | 4 +---
2 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-graphics/libva/libva.inc
b/meta/recipes-graphics/libva/libva.inc
index bcf9757c1a..0e2721e291 100644
--- a/meta/recipes-graphics/libva/libva.inc
+++ b/meta/recipes-graphics/libva/libva.inc
@@ -27,3 +27,10 @@ UPSTREAM_CHECK_URI =
"https://github.com/intel/libva/releases;
DEPENDS = "libdrm"
inherit meson pkgconfig
+
+PACKAGECONFIG:append = " \
+${@bb.utils.filter('DISTRO_FEATURES', 'wayland', d)} \
+"
+
+PACKAGECONFIG[wayland] = "-Dwith_wayland=yes,-Dwith_wayland=no,wayland-native
wayland"
+
diff --git a/meta/recipes-graphics/libva/libva_2.13.0.bb
b/meta/recipes-graphics/libva/libva_2.13.0.bb
index ed2be289fc..a8c6355b01 100644
--- a/meta/recipes-graphics/libva/libva_2.13.0.bb
+++ b/meta/recipes-graphics/libva/libva_2.13.0.bb
@@ -2,14 +2,12 @@ require libva.inc
PACKAGECONFIG ??= " \
${@bb.utils.contains('DISTRO_FEATURES', 'x11 opengl', 'glx', '', d)} \
-${@bb.utils.filter('DISTRO_FEATURES', 'x11 wayland', d)} \
+${@bb.utils.filter('DISTRO_FEATURES', 'x11', d)} \
"
PACKAGECONFIG[x11] = "-Dwith_x11=yes,-Dwith_x11=no,virtual/libx11 libxext
libxfixes"
PACKAGECONFIG[glx] = "-Dwith_glx=yes,-Dwith_glx=no,virtual/mesa"
-PACKAGECONFIG[wayland] = "-Dwith_wayland=yes,-Dwith_wayland=no,wayland-native
wayland"
-
PACKAGES =+ "${PN}-x11 ${PN}-glx ${PN}-wayland"
RDEPENDS:${PN}-x11 =+ "${PN}"
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55544): https://lists.yoctoproject.org/g/yocto/message/55544
Mute This Topic: https://lists.yoctoproject.org/mt/87630461/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [meta-rockchip][PATCH] trusted-firmware-a: Pin to use gcc for now
tf-a built with clang is bloated for rk3399 SOCs with 2.6+ it needs looking into, until then use gcc always to build it Signed-off-by: Khem Raj Cc: Jon Mason Cc: Ross Burton --- .../trusted-firmware-a/trusted-firmware-a_%.bbappend | 7 +++ 1 file changed, 7 insertions(+) diff --git a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend index 074d0e0..513cea1 100644 --- a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend +++ b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend @@ -12,3 +12,10 @@ SRC_URI += "\ file://0001-plat_macros.S-Use-compatible-.asciz-asm-directive.patch \ file://0001-pmu-Do-not-mark-already-defined-functions-as-weak.patch \ " + + +# code bloats with clang and results in error below now +# | aarch64-yoe-linux-musl-ld: region `PMUSRAM' overflowed by 3928 bytes +# this needs fixing until then use gcc +TOOLCHAIN:rk3399 = "gcc" + -- 2.34.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#55543): https://lists.yoctoproject.org/g/yocto/message/55543 Mute This Topic: https://lists.yoctoproject.org/mt/87627042/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] standard SDK build with clang compiler built into kernel image
Thanks again, will take a look and give it a try... -Original Message- From: Khem Raj Sent: Thursday, December 9, 2021 2:55 PM To: Monsees, Steven C (US) Cc: yocto@lists.yoctoproject.org Subject: Re: [yocto] standard SDK build with clang compiler built into kernel image External Email Alert This email has been sent from an account outside of the BAE Systems network. Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros. For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar. This is a known issue look at https://github.com/kraj/meta-clang/issues/119 You can workaround it by https://github.com/kraj/meta-clang/issues/119#issuecomment-518317888 On Thu, Dec 9, 2021 at 11:22 AM Monsees, Steven C (US) via lists.yoctoproject.org wrote: > > > > I am building clang compiler support into my kernel, to support igc > (intel graphics compiler)… > > > > When I build the standard SDK it list a series of specific clang/llvm issues > but successfully completes the SDK setup/install. > > The SDK looks to have everything in place, and basic functionality is > working… > > > > I do not see these messages when I remove the clang component. > > > > Can someone explain what is happening here ?, is it a known issue ?, is > there patch available ? > > > > I am building a “zeus” 3.0.4 based kernel, for centos… > > > > -bash-4.2$ cd sdk > > -bash-4.2$ ls > > limws-glibc-x86_64-aiox_orange-corei7-64-toolchain-3.0.4.host.manifest > > limws-glibc-x86_64-aiox_orange-corei7-64-toolchain-3.0.4.sh > > limws-glibc-x86_64-aiox_orange-corei7-64-toolchain-3.0.4.target.manife > st > > limws-glibc-x86_64-aiox_orange-corei7-64-toolchain-3.0.4.testdata.json > > -bash-4.2$ sudo > ./limws-glibc-x86_64-aiox_orange-corei7-64-toolchain-3.0.4.sh > > [sudo] password for smonsees: > > LIMWS (BAE LIMWS base distro) SDK installer version 3.0.4 > > = > > Enter target directory for SDK (default: /opt/limws/3.0.4): > /disk0/scratch/smonsees/yocto/sdk_3.0.4 > > You are about to install the SDK to > "/disk0/scratch/smonsees/yocto/sdk_3.0.4". Proceed [Y/n]? Y > > Extracting > SDK... > .. > .. > .. > .. > .. > .. > .. > .. > .. > .. > .. > .. > .. > .. > .. > ..done > > Setting it up...ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/clang-tidy, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-cxxdump, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-ar, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-symbolizer, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/clang-9, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-as, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/clang-extdef-mapping, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/clang-reorder-fields, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-mca, >
Re: [yocto] standard SDK build with clang compiler built into kernel image
This is a known issue look at https://github.com/kraj/meta-clang/issues/119 You can workaround it by https://github.com/kraj/meta-clang/issues/119#issuecomment-518317888 On Thu, Dec 9, 2021 at 11:22 AM Monsees, Steven C (US) via lists.yoctoproject.org wrote: > > > > I am building clang compiler support into my kernel, to support igc (intel > graphics compiler)… > > > > When I build the standard SDK it list a series of specific clang/llvm issues > but successfully completes the SDK setup/install. > > The SDK looks to have everything in place, and basic functionality is working… > > > > I do not see these messages when I remove the clang component. > > > > Can someone explain what is happening here ?, is it a known issue ?, is > there patch available ? > > > > I am building a “zeus” 3.0.4 based kernel, for centos… > > > > -bash-4.2$ cd sdk > > -bash-4.2$ ls > > limws-glibc-x86_64-aiox_orange-corei7-64-toolchain-3.0.4.host.manifest > > limws-glibc-x86_64-aiox_orange-corei7-64-toolchain-3.0.4.sh > > limws-glibc-x86_64-aiox_orange-corei7-64-toolchain-3.0.4.target.manifest > > limws-glibc-x86_64-aiox_orange-corei7-64-toolchain-3.0.4.testdata.json > > -bash-4.2$ sudo ./limws-glibc-x86_64-aiox_orange-corei7-64-toolchain-3.0.4.sh > > [sudo] password for smonsees: > > LIMWS (BAE LIMWS base distro) SDK installer version 3.0.4 > > = > > Enter target directory for SDK (default: /opt/limws/3.0.4): > /disk0/scratch/smonsees/yocto/sdk_3.0.4 > > You are about to install the SDK to > "/disk0/scratch/smonsees/yocto/sdk_3.0.4". Proceed [Y/n]? Y > > Extracting > SDK...done > > Setting it up...ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/clang-tidy, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-cxxdump, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-ar, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-symbolizer, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/clang-9, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-as, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/clang-extdef-mapping, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/clang-reorder-fields, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-mca, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/clang-apply-replacements, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-dwarfdump, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-elfabi, > interp size = 72 and 95 is needed. > > ERROR: could not relocate > /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/lldb-instr, > interp size = 72 and 95 is needed. > > ERROR: could not relocate >
[yocto] Yocto Autobuilder: Latency Monitor and AB-INT - Meeting notes: Dec 9, 2021
YP AB Intermittent failures meeting === https://windriver.zoom.us/j/3696693975 Attendees: Richard, Trevor, Randy, Saul, AlexB Summary: -- People have been busy with other work so this is mostly a duplicate of the previous minutes with some cyptic? IRC chat logs added below. -- Ptest results continue to improve yet again but there's still room for even more improvement. Alex made a graph of the number of AB INT issues per week: https://bootlin.com/~alexandre/SWAT_stats.png We assume that week 15, 16 was when the RCU bug in he kernel started being a problem and week 29 was when it go fixed but more careful analysis is required. The make/ninja load average limit is in but it's not clear if it's effective yet and it breaks dunfell. Trevor has a build of dunfell that with some patches appears to work. If anyone wants to help, we could use more eyes on the logs, particularly the summary logs and understanding iostat # when the dd test times out. Plans for the week: === Richard: M1 Alex: look into Rest API for BZ as part of Triage. Sakib: hook more responsive load average in to latency test. (v3) : Add PSI (/proc/pressure/*) when available Trevor: No AB work Saul: No AB work Randy: PSI, simple experiments to learn what's 'normal', make some PSI graphs! Idea: bitbake/make/ninja use /proc/pressure to throttle builds? ../Randy Meeting Notes: == Cryptic notes this week since I don't have time for a proper summary! [09:01] Agenda Items? [09:01] 1. PSI /proc/pressure see: https://www.kernel.org/doc/html/latest/accounting/psi.html [09:01] 2. Status of AB [09:02] 3. Randy promises valgrind patches (again!). Discussion: Randy explained what the PSI proc data was and how overloaded ubuntu2004-ty-2.yocto.io was for most of a 25 hour logging window. Typical high load data is: pressure.cpu some avg10=0.00 avg60=0.00 avg300=1.12 total=8891584119 some avg10=0.00 avg60=0.00 avg300=1.00 total=8891596517 some avg10=0.00 avg60=0.00 avg300=0.90 total=8891613258 some avg10=0.00 avg60=0.00 avg300=0.81 total=8891631326 pressure.memory some avg10=0.00 avg60=0.00 avg300=0.00 total=237120503 full avg10=0.00 avg60=0.00 avg300=0.00 total=194500170 some avg10=0.00 avg60=0.00 avg300=0.00 total=237121370 full avg10=0.00 avg60=0.00 avg300=0.00 total=194500170 pressure.io some avg10=65.22 avg60=56.24 avg300=40.82 total=142092410628 full avg10=65.22 avg60=56.23 avg300=40.28 total=134090291475 some avg10=48.50 avg60=52.56 avg300=41.42 total=142106526703 full avg10=48.50 avg60=52.56 avg300=40.93 total=134104406782 This is just: for i in pressure.cpu pressure.memory pressure.io; do \ echo $i; tail -4 $i; \ done There are two lines per call for some of the /proc/pressure files: $ wc -l pressure* 3000 pressure.cpu 6000 pressure.io 6000 pressure.memory Looking at the max io load for the times when the 'full' system is overloaded: $ grep full pressure.io | cat -n > pressure.io-full.numbered $ sed -e 's/=/ /g' pressure.io-full.numbered | sort -k 4 -n | tail -2 1710 full avg10 97.52 avg60 93.85 avg300 92.29 total 124322928244 1699 full avg10 97.57 avg60 93.16 avg300 91.36 total 124015261496 # make a link so we have *full.numbered files for each subsystem: $ ln -s pressure.cpu.numbered pressure.cpu-ful.numbered $ for i in pressure.cpu pressure.memory pressure.io; do \ echo $i; egrep ' 1710| 1699' $i-full.numbered; \ done pressure.cpu 1699 some avg10=0.00 avg60=0.00 avg300=0.00 total=7340981927 1710 some avg10=0.00 avg60=0.00 avg300=0.00 total=7341522636 pressure.memory 1699 full avg10=0.00 avg60=0.00 avg300=0.00 total=131800420 1710 full avg10=0.00 avg60=0.00 avg300=0.00 total=131800502 pressure.io 1699 full avg10=97.57 avg60=93.16 avg300=91.36 total=124015261496 1710 full avg10=97.52 avg60=93.85 avg300=92.29 total=124322928244 Conclusion, no cpu, memory contention, lots of IO -- clean-up or ??? [09:22] read-only YP BZ database query to find "AB-INT" build failures, find build and highlight in "non-release" AB build summary. [09:23] add /proc/pressure info to test results logs. Sakib and I may do this, else Alex in January [09:24] network access: weird AB bugs: DNS or connextion failure, at times even qemu net connection fails! [09:26] systemd-networkd at times monitors and maybe even changes (if up/down?) tap interfaces This seems to be hard-coded, mandatory behaviour in systemd managed distros. [09:26] Test system, start / stop qemu instances in a loop. [09:29] say: 16 qemus booting core-image-minimal and doing a simple test such as a network connection (download curl), along with stress --mumble-args to load the host sytem to simulate a build. [09:30] vmeson:
[yocto] standard SDK build with clang compiler built into kernel image
I am building clang compiler support into my kernel, to support igc (intel graphics compiler)... When I build the standard SDK it list a series of specific clang/llvm issues but successfully completes the SDK setup/install. The SDK looks to have everything in place, and basic functionality is working... I do not see these messages when I remove the clang component. Can someone explain what is happening here ?, is it a known issue ?, is there patch available ? I am building a "zeus" 3.0.4 based kernel, for centos... -bash-4.2$ cd sdk -bash-4.2$ ls limws-glibc-x86_64-aiox_orange-corei7-64-toolchain-3.0.4.host.manifest limws-glibc-x86_64-aiox_orange-corei7-64-toolchain-3.0.4.sh limws-glibc-x86_64-aiox_orange-corei7-64-toolchain-3.0.4.target.manifest limws-glibc-x86_64-aiox_orange-corei7-64-toolchain-3.0.4.testdata.json -bash-4.2$ sudo ./limws-glibc-x86_64-aiox_orange-corei7-64-toolchain-3.0.4.sh [sudo] password for smonsees: LIMWS (BAE LIMWS base distro) SDK installer version 3.0.4 = Enter target directory for SDK (default: /opt/limws/3.0.4): /disk0/scratch/smonsees/yocto/sdk_3.0.4 You are about to install the SDK to "/disk0/scratch/smonsees/yocto/sdk_3.0.4". Proceed [Y/n]? Y Extracting SDK...done Setting it up...ERROR: could not relocate /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/clang-tidy, interp size = 72 and 95 is needed. ERROR: could not relocate /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-cxxdump, interp size = 72 and 95 is needed. ERROR: could not relocate /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-ar, interp size = 72 and 95 is needed. ERROR: could not relocate /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-symbolizer, interp size = 72 and 95 is needed. ERROR: could not relocate /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/clang-9, interp size = 72 and 95 is needed. ERROR: could not relocate /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-as, interp size = 72 and 95 is needed. ERROR: could not relocate /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/clang-extdef-mapping, interp size = 72 and 95 is needed. ERROR: could not relocate /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/clang-reorder-fields, interp size = 72 and 95 is needed. ERROR: could not relocate /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-mca, interp size = 72 and 95 is needed. ERROR: could not relocate /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/clang-apply-replacements, interp size = 72 and 95 is needed. ERROR: could not relocate /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-dwarfdump, interp size = 72 and 95 is needed. ERROR: could not relocate /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-elfabi, interp size = 72 and 95 is needed. ERROR: could not relocate /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/lldb-instr, interp size = 72 and 95 is needed. ERROR: could not relocate /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/c-index-test, interp size = 72 and 95 is needed. ERROR: could not relocate /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/clang-doc, interp size = 72 and 95 is needed. ERROR: could not relocate /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/lldb-tblgen, interp size = 72 and 95 is needed. ERROR: could not relocate
Re: [yocto] honister - errors while patching net-snmp 5.9
On Thu, Dec 9, 2021 at 7:59 AM Ori Pessach wrote: > > With the latest honister code I'm getting this error: > > ERROR: net-snmp-5.9.1-r0 do_patch: Applying patch > '0001-snmplib-keytools.c-Don-t-check-for-return-from-EVP_M.patch' on target > directory > '/media/ori/Linux-Backup/poky-intel/build/tmp/work/corei7-64-poky-linux/net-snmp/5.9.1-r0/net-snmp-5.9.1' > Command Error: 'quilt --quiltrc > /media/ori/Linux-Backup/poky-intel/build/tmp/work/corei7-64-poky-linux/net-snmp/5.9.1-r0/recipe-sysroot-native/etc/quiltrc > push' exited with 0 Output: > stdout: Applying patch > 0001-snmplib-keytools.c-Don-t-check-for-return-from-EVP_M.patch > patching file snmplib/keytools.c > Hunk #1 FAILED at 186. > 1 out of 1 hunk FAILED -- rejects in file snmplib/keytools.c > Patch 0001-snmplib-keytools.c-Don-t-check-for-return-from-EVP_M.patch does > not apply (enforce with -f) > > Removing that patch from the recipe lets the build continue. The changes are the same as master and it applies fine on master without any patch fuzz either, can you check if there are some other patches are applied to this recipe from other layers. I wonder if someone else can reproduce it on honister ? > > Ori Pessach > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#55538): https://lists.yoctoproject.org/g/yocto/message/55538 Mute This Topic: https://lists.yoctoproject.org/mt/87614514/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] Specify systemd startup order for volatile-bind and network setup
Hi, I have a read-only rootfs created with IMAGE_FEATURES:append=read-only-rootfs and a few files located in a read/write partition which are defined in the volatile-bind recipe. So far so good. But one file located in the rw partition is the network configuration (/usr/lib/systemd/network/20-wired.network). Unfortunately the network is loaded before the volatile-binds are mounted. Does some one know, how to force volatile-bind to be mounted before the network is initialized? I'm using systemd and dunfell. Thanks, Silvan -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#55537): https://lists.yoctoproject.org/g/yocto/message/55537 Mute This Topic: https://lists.yoctoproject.org/mt/87615908/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] Minutes: Yocto Project Weekly Triage Meeting 12/9/2021
*Wiki: *https://wiki.yoctoproject.org/wiki/Bug_Triage *Attendees: *Alexandre, Anuj, Bruce, Daiane, Joshua, Michael, Ross, Saul, Stephen, Steve, Randy, Richard, Tim, Trevor *ARs:* N/A *Notes:* There was no meeting for 12/2/2021 due to Yocto Summit *Medium+ 3.5 Unassigned Enhancements/Bugs: *75 (Last week 73) *Medium+ 3.99 Unassigned Enhancements/Bugs: *38**(Last week 38) *AB Bugs: *67 (Last week 61) -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#55536): https://lists.yoctoproject.org/g/yocto/message/55536 Mute This Topic: https://lists.yoctoproject.org/mt/87615375/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] honister - errors while patching net-snmp 5.9
With the latest honister code I'm getting this error: ERROR: net-snmp-5.9.1-r0 do_patch: Applying patch '0001-snmplib-keytools.c-Don-t-check-for-return-from-EVP_M.patch' on target directory '/media/ori/Linux-Backup/poky-intel/build/tmp/work/corei7-64-poky-linux/net-snmp/5.9.1-r0/net-snmp-5.9.1' Command Error: 'quilt --quiltrc /media/ori/Linux-Backup/poky-intel/build/tmp/work/corei7-64-poky-linux/net-snmp/5.9.1-r0/recipe-sysroot-native/etc/quiltrc push' exited with 0 Output: stdout: Applying patch 0001-snmplib-keytools.c-Don-t-check-for-return-from-EVP_M.patch patching file snmplib/keytools.c Hunk #1 FAILED at 186. 1 out of 1 hunk FAILED -- rejects in file snmplib/keytools.c Patch 0001-snmplib-keytools.c-Don-t-check-for-return-from-EVP_M.patch does not apply (enforce with -f) Removing that patch from the recipe lets the build continue. Ori Pessach -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#55535): https://lists.yoctoproject.org/g/yocto/message/55535 Mute This Topic: https://lists.yoctoproject.org/mt/87614514/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] kwayland-server-5.23.1
Hi Team, I am facing a problem with the Kwayland-server package issue. Can anybody know about this package issue or patchwork can you please guide me. ERROR: kwayland-server-5.23.1-r0 do_compile: Execution of '/home/sample-kde/build/tmp-glibc/work/riscv64-oe-linux/kwayland-server/5.23.1-r0/temp/run.do_compile.23397' failed with exit code 1: ninja: error: '/usr/share/wayland/wayland.xml', needed by 'src/server/qwayland-server-wayland.cpp', missing and no known rule to make it WARNING: exit code 1 from a shell command. ERROR: Logfile of failure stored in: /home/sample-kde/build/tmp-glibc/work/riscv64-oe-linux/kwayland-server/5.23.1-r0/temp/log.do_compile.23397 Log data follows: | DEBUG: Executing shell function do_compile | NOTE: VERBOSE=1 cmake --build /home/sateesh/sample-kde/build/tmp-glibc/work/riscv64-oe-linux/kwayland-server/5.23.1-r0/build --target all -- | ninja: error: '/usr/share/wayland/wayland.xml', needed by 'src/server/qwayland-server-wayland.cpp', missing and no known rule to make it | WARNING: exit code 1 from a shell command. | ERROR: Execution of '/home/sample-kde/build/tmp-glibc/work/riscv64-oe-linux/kwayland-server/5.23.1-r0/temp/run.do_compile.23397' failed with exit code 1: | ninja: error: '/usr/share/wayland/wayland.xml', needed by 'src/server/qwayland-server-wayland.cpp', missing and no known rule to make it | WARNING: exit code 1 from a shell command. | ERROR: Task (/home/sample-kde/yocto-meta-kde/recipes-plasma/kwayland-server_5.23.1.bb:do_compile) failed with exit code '1' NOTE: Tasks Summary: Attempted 3506 tasks of which 3500 didn't need to be rerun and 1 failed. Summary: 1 task failed: /home/sample-kde/yocto-meta-kde/recipes-plasma/kwayland-server_5.23.1.bb:do_compile Summary: There was 1 ERROR message shown, returning a non-zero exit code. -- Regards, Sateesh -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#55534): https://lists.yoctoproject.org/g/yocto/message/55534 Mute This Topic: https://lists.yoctoproject.org/mt/87611519/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][linux-yocto v5.10] fix patches for marvell octeon
In message: [linux-yocto][linux-yocto v5.10] fix patches for marvell octeon on 09/12/2021 Ruiqiang Hao wrote: > Hi Bruce, > > Please help to merge this patch into our linux-yocto repo. > > repo: > linux-yocto > branch: > v5.10/standard/cn-sdkv5.4/octeon > v5.10/standard/preempt-rt/cn-sdkv5.4/octeon merged. Bruce > > Thanks, > Ruiqiang -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10733): https://lists.yoctoproject.org/g/linux-yocto/message/10733 Mute This Topic: https://lists.yoctoproject.org/mt/87561697/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][v5.10/standard/x86 and v5.10/standard/preempt-rt/x86][PATCH] net: stmmac: fix a merge error in stmmac_main.c
It's amazing the amount of modifications the different SDKs and BSPs
are doing to this driver. -stable has consistently confliced with them
all for the past 5 or 6 updates .. so these sorts of things will happen
from time to time.
Thanks for the fixup, this is now merged.
Bruce
In message: [linux-yocto][v5.10/standard/x86 and
v5.10/standard/preempt-rt/x86][PATCH] net: stmmac: fix a merge error in
stmmac_main.c
on 09/12/2021 Yongxin Liu wrote:
> Fix the following build error which is introduced in merge commits
> ef48d3d353b6 ("Merge branch 'v5.10/standard/base' into v5.10/standard/x86")
> and
> c552a743a2fe ("Merge branch 'v5.10/standard/base' into
> v5.10/standard/preempt-rt/x86").
>
> linux-yocto/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c: In function
> ‘stmmac_suspend’:
> linux-yocto/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c:7667:17: error:
> ‘ret’
> undeclared (first use in this function); did you mean ‘net’?
> 7667 | ret = priv->plat->remove_phy_conv(priv->mii,
> | ^~~
> | net
> linux-yocto/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c:7667:17: note:
> each
> undeclared identifier is reported only once for each function it appears in
> make[6]: *** [linux-yocto/scripts/Makefile.build:280:
> drivers/net/ethernet/stmicro/stmmac/stmmac_main.o] Error 1
>
> Signed-off-by: Yongxin Liu
> ---
> drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> index ec532532c4b9..e84aec7767f1 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> @@ -7645,6 +7645,7 @@ int stmmac_suspend(struct device *dev)
> struct net_device *ndev = dev_get_drvdata(dev);
> struct stmmac_priv *priv = netdev_priv(ndev);
> u32 chan;
> + int ret;
>
> #ifdef CONFIG_STMMAC_NETWORK_PROXY
> stmmac_pm_suspend(priv, priv, ndev);
> --
> 2.31.1
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10732):
https://lists.yoctoproject.org/g/linux-yocto/message/10732
Mute This Topic: https://lists.yoctoproject.org/mt/87607809/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] netkit-ftp for yocto
Hello Guys
I have installed netkit-ftp-0.17-r0 version successfully but i am *not able to
get -4 and -6 option* with using ftp -help
$ ftp -help
Usage: { ftp | pftp } [-46pinegvtd] [hostname]
-p: enable passive mode (default for pftp)
-i: turn off prompting during mget
-n: inhibit auto-login
-e: disable readline support, if present
-g: disable filename globbing
-v: verbose mode
-t: enable packet tracing [nonfunctional]
-d: enable debugging
not getting ipv4 and ipv6 option
-4: use IPv4 addresses only
-6: use IPv6, nothing else
if some package or something is missing, please update me so that i can modify.
T
lavkhush
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55533): https://lists.yoctoproject.org/g/yocto/message/55533
Mute This Topic: https://lists.yoctoproject.org/mt/87609516/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] [yocto-kernel-cache][PATCH 1/1] cfg/debug: add kcov kernel configs
KCOV exposes kernel code coverage information in a form suitable for coverage-guided fuzzing. This debug feature can be enabled to add support for kernel fuzzing (with tools such as syzkaller). Signed-off-by: Ovidiu Panait --- cfg/debug/kcov/debug-kcov.cfg | 4 cfg/debug/kcov/debug-kcov.scc | 5 + 2 files changed, 9 insertions(+) create mode 100644 cfg/debug/kcov/debug-kcov.cfg create mode 100644 cfg/debug/kcov/debug-kcov.scc diff --git a/cfg/debug/kcov/debug-kcov.cfg b/cfg/debug/kcov/debug-kcov.cfg new file mode 100644 index ..9cdd37ce --- /dev/null +++ b/cfg/debug/kcov/debug-kcov.cfg @@ -0,0 +1,4 @@ +# SPDX-License-Identifier: MIT +CONFIG_KCOV=y +CONFIG_KCOV_ENABLE_COMPARISONS=y +CONFIG_KCOV_INSTRUMENT_ALL=y diff --git a/cfg/debug/kcov/debug-kcov.scc b/cfg/debug/kcov/debug-kcov.scc new file mode 100644 index ..325c6f99 --- /dev/null +++ b/cfg/debug/kcov/debug-kcov.scc @@ -0,0 +1,5 @@ +# SPDX-License-Identifier: MIT +define KFEATURE_DESCRIPTION "Enable kernel code coverage support" +define KFEATURE_COMPATIBILITY all + +kconf non-hardware debug-kcov.cfg -- 2.25.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10731): https://lists.yoctoproject.org/g/linux-yocto/message/10731 Mute This Topic: https://lists.yoctoproject.org/mt/87609326/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] [PATCH] octeontx2: vf: Avoid canceling an uninitialized work queue
From: Ruiqiang Hao
For SMQVF function, reset_task work queue is uninitialized, if we cancel
this work queue, following calltrace will be caused because work->func is
NULL. There is no need to cancel reset_task work queue for SMQVF function.
WARNING: CPU: 2 PID: 1 at kernel/workqueue.c:3038 __flush_work+0x10c/0x120
CPU: 2 PID: 1 Comm: systemd-shutdow Not tainted 5.10.76-yocto-standard #1
Hardware name: Marvell OcteonTX CN96XX board (DT)
pstate: 6049 (nZCv daif +PAN UAO -TCO BTYPE=-)
pc : __flush_work+0x10c/0x120
lr : __cancel_work_timer+0x154/0x1c4
sp : 8000140efa90
x29: 8000140efa90 x28: 0001024c0040
x27: x26: 80001143e290
x25: 0001 x24: 0001024c0040
x23: x22:
x21: x20: 00014c627958
x19: 0001 x18:
x17: x16: 0006
x15: 800013196a20 x14: 2820303030303030
x13: 3030303030303030 x12: 303020746e657261
x11: 00f1 x10: 7b31403b
x9 : 8000100696f4 x8 : 8000126b68f0
x7 : x6 : 800011d4c000
x5 : 800011d4c730 x4 : 0003
x3 : x2 : 0001024c0040
x1 : 0001 x0 :
Call trace:
__flush_work+0x10c/0x120
__cancel_work_timer+0x154/0x1c4
cancel_work_sync+0x20/0x2c
otx2vf_remove+0x3c/0x140
pci_device_shutdown+0x40/0x50
device_shutdown+0x140/0x30c
kernel_power_off+0x44/0x80
__do_sys_reboot+0x170/0x270
__arm64_sys_reboot+0x30/0x40
el0_svc_common.constprop.0+0x88/0x1a0
do_el0_svc+0x34/0xc0
el0_svc+0x20/0x30
el0_sync_handler+0xa4/0x150
el0_sync+0x180/0x1c0
irq event stamp: 14562824
Signed-off-by: Ruiqiang Hao
---
drivers/net/ethernet/marvell/octeontx2/nic/otx2_vf.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/marvell/octeontx2/nic/otx2_vf.c
b/drivers/net/ethernet/marvell/octeontx2/nic/otx2_vf.c
index 59162267969d..067f222f2502 100644
--- a/drivers/net/ethernet/marvell/octeontx2/nic/otx2_vf.c
+++ b/drivers/net/ethernet/marvell/octeontx2/nic/otx2_vf.c
@@ -774,10 +774,9 @@ static void otx2vf_remove(struct pci_dev *pdev)
vf = netdev_priv(netdev);
- cancel_work_sync(>reset_task);
-
if (otx2smqvf_remove(vf)) {
otx2_unregister_dl(vf);
+ cancel_work_sync(>reset_task);
unregister_netdev(netdev);
}
--
2.32.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10730):
https://lists.yoctoproject.org/g/linux-yocto/message/10730
Mute This Topic: https://lists.yoctoproject.org/mt/87608516/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto][linux-yocto v5.10] fix patches for marvell octeon
Hi Bruce, Please help to merge this patch into our linux-yocto repo. repo: linux-yocto branch: v5.10/standard/cn-sdkv5.4/octeon v5.10/standard/preempt-rt/cn-sdkv5.4/octeon Thanks, Ruiqiang -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10729): https://lists.yoctoproject.org/g/linux-yocto/message/10729 Mute This Topic: https://lists.yoctoproject.org/mt/87561697/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
