Re: [oe] Help with Inclusive Language in OpenEmbedded/Yocto Project
On 12/6/21 5:01 PM, Jon Mason wrote:
please add me to the list.
-armin
This email is a follow-up from the session held on Friday at theThanks for driving this.
OpenEmbedded Developer's Virtual Meeting (see
https://www.openembedded.org/wiki/OEDVM_Nov_2021)
The session was not recorded, but the slides can be found at
https://docs.google.com/presentation/d/146ueVVTMeA8JI43wqv5kFmdYEygqqmfGH0z1VRL2bDA/edit?usp=sharing
The outcome from the discussion was that inclusive language changes
are something that we want to accomplish in the kirkstone release
timeframe (with an exception for the "master" branch name, which will
be handled at a future date).
There has already been a pass at collecting the needed changes at
https://wiki.yoctoproject.org/wiki/Inclusive_language
This is not as simple as a find/replace of offending words. There is
a desire for backward compatibility or to provide some kind of "you
want X, which is now Y" (which complicates things).
The intention of this email is to see who is interested in helping
out. Once we know how many people are available and what time frames,
we can plan out a roadmap. So, please email me (or respond to this
thread publicly) and I'll add you to the list. There will then be a
follow-up zoom call in the next week or so to plan out the roadmap.
We will document the roadmap and everything else on the YP wiki page above.
Questions and comments are welcome, but not interested in debating the
necessity or timeframe of this task. It has already been decided.
please add me to the list.
-armin
Thanks,
Jon
[meta-rockchip][PATCH v2] override syntax fixup
Trevor Woerner
The _virtual notation is not an override. These syntax "fixes" need to be
reverted.
In the case of the kernel override, when it was added, the rock-pi-e needed
the latest kernel (linux-yocto-dev) but now the default linux-yocto kernel
will suffice. So this mistake actually switched the rock-pi-e from
linux-yocto-dev back to linux-yocto inadvertently but at a time when
linux-yocto-dev was no longer required.
In the case of the bootloader overrides, u-boot was always the default, so
these overrides were always redundant.
Therefore, in the end, simply removing these overrides is the best way
forward (considering these aren't doing anything, and the builds are working
fine regardless).
Signed-off-by: Trevor Woerner <twoerner@...>
---
conf/machine/include/rk3288.inc | 1 -
conf/machine/include/rk3328.inc | 2 --
conf/machine/include/rk3399.inc | 2 --
conf/machine/include/rockchip-defaults.inc | 1 -
conf/machine/rock-pi-e.conf | 2 --
5 files changed, 8 deletions(-)
diff --git a/conf/machine/include/rk3288.inc b/conf/machine/include/rk3288.inc
index 5b84e94..1d4a0e3 100644
--- a/conf/machine/include/rk3288.inc
+++ b/conf/machine/include/rk3288.inc
@@ -12,5 +12,4 @@ SERIAL_CONSOLES = "115200;ttyS2"
KBUILD_DEFCONFIG ?= "multi_v7_defconfig"
KERNEL_IMAGETYPE = "zImage"
-PREFERRED_PROVIDER:virtual/bootloader ?= "u-boot"
UBOOT_SUFFIX ?= "bin"
diff --git a/conf/machine/include/rk3328.inc b/conf/machine/include/rk3328.inc
index 0f3a730..acc9afd 100644
--- a/conf/machine/include/rk3328.inc
+++ b/conf/machine/include/rk3328.inc
@@ -19,5 +19,3 @@ TFA_BUILD_TARGET = "bl31"
UBOOT_SUFFIX ?= "itb"
UBOOT_ENTRYPOINT ?= "0x06000000"
-
-PREFERRED_PROVIDER:virtual/bootloader ?= "u-boot"
diff --git a/conf/machine/include/rk3399.inc b/conf/machine/include/rk3399.inc
index 09c87c0..1e6c3b6 100644
--- a/conf/machine/include/rk3399.inc
+++ b/conf/machine/include/rk3399.inc
@@ -19,5 +19,3 @@ TFA_BUILD_TARGET = "bl31"
UBOOT_SUFFIX ?= "itb"
UBOOT_ENTRYPOINT ?= "0x06000000"
-
-PREFERRED_PROVIDER:virtual/bootloader ?= "u-boot"
diff --git a/conf/machine/include/rockchip-defaults.inc b/conf/machine/include/rockchip-defaults.inc
index 455cca8..ca94249 100644
--- a/conf/machine/include/rockchip-defaults.inc
+++ b/conf/machine/include/rockchip-defaults.inc
@@ -5,7 +5,6 @@ PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
KCONFIG_MODE ?= "alldefconfig"
# xserver
-PREFERRED_PROVIDER:virtual/xserver = "xserver-xorg"
XSERVER = " \
xserver-xorg \
xserver-xorg-utils \
diff --git a/conf/machine/rock-pi-e.conf b/conf/machine/rock-pi-e.conf
index 7f49c9f..0e2856f 100644
--- a/conf/machine/rock-pi-e.conf
+++ b/conf/machine/rock-pi-e.conf
@@ -7,9 +7,7 @@ require conf/machine/include/rk3328.inc
MACHINEOVERRIDES =. "rock-pi-e:"
-PREFERRED_PROVIDER:virtual/kernel = "linux-yocto-dev"
KERNEL_DEVICETREE = "rockchip/rk3328-rock-pi-e.dtb"
MACHINE_EXTRA_RRECOMMENDS += "kernel-modules"
-PREFERRED_PROVIDER:virtual/bootloader = "u-boot"
UBOOT_MACHINE = "rock-pi-e-rk3328_defconfig"
--
2.34.1.75.gabe6bb3905
reverted.
In the case of the kernel override, when it was added, the rock-pi-e needed
the latest kernel (linux-yocto-dev) but now the default linux-yocto kernel
will suffice. So this mistake actually switched the rock-pi-e from
linux-yocto-dev back to linux-yocto inadvertently but at a time when
linux-yocto-dev was no longer required.
In the case of the bootloader overrides, u-boot was always the default, so
these overrides were always redundant.
Therefore, in the end, simply removing these overrides is the best way
forward (considering these aren't doing anything, and the builds are working
fine regardless).
Signed-off-by: Trevor Woerner <twoerner@...>
---
conf/machine/include/rk3288.inc | 1 -
conf/machine/include/rk3328.inc | 2 --
conf/machine/include/rk3399.inc | 2 --
conf/machine/include/rockchip-defaults.inc | 1 -
conf/machine/rock-pi-e.conf | 2 --
5 files changed, 8 deletions(-)
diff --git a/conf/machine/include/rk3288.inc b/conf/machine/include/rk3288.inc
index 5b84e94..1d4a0e3 100644
--- a/conf/machine/include/rk3288.inc
+++ b/conf/machine/include/rk3288.inc
@@ -12,5 +12,4 @@ SERIAL_CONSOLES = "115200;ttyS2"
KBUILD_DEFCONFIG ?= "multi_v7_defconfig"
KERNEL_IMAGETYPE = "zImage"
-PREFERRED_PROVIDER:virtual/bootloader ?= "u-boot"
UBOOT_SUFFIX ?= "bin"
diff --git a/conf/machine/include/rk3328.inc b/conf/machine/include/rk3328.inc
index 0f3a730..acc9afd 100644
--- a/conf/machine/include/rk3328.inc
+++ b/conf/machine/include/rk3328.inc
@@ -19,5 +19,3 @@ TFA_BUILD_TARGET = "bl31"
UBOOT_SUFFIX ?= "itb"
UBOOT_ENTRYPOINT ?= "0x06000000"
-
-PREFERRED_PROVIDER:virtual/bootloader ?= "u-boot"
diff --git a/conf/machine/include/rk3399.inc b/conf/machine/include/rk3399.inc
index 09c87c0..1e6c3b6 100644
--- a/conf/machine/include/rk3399.inc
+++ b/conf/machine/include/rk3399.inc
@@ -19,5 +19,3 @@ TFA_BUILD_TARGET = "bl31"
UBOOT_SUFFIX ?= "itb"
UBOOT_ENTRYPOINT ?= "0x06000000"
-
-PREFERRED_PROVIDER:virtual/bootloader ?= "u-boot"
diff --git a/conf/machine/include/rockchip-defaults.inc b/conf/machine/include/rockchip-defaults.inc
index 455cca8..ca94249 100644
--- a/conf/machine/include/rockchip-defaults.inc
+++ b/conf/machine/include/rockchip-defaults.inc
@@ -5,7 +5,6 @@ PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
KCONFIG_MODE ?= "alldefconfig"
# xserver
-PREFERRED_PROVIDER:virtual/xserver = "xserver-xorg"
XSERVER = " \
xserver-xorg \
xserver-xorg-utils \
diff --git a/conf/machine/rock-pi-e.conf b/conf/machine/rock-pi-e.conf
index 7f49c9f..0e2856f 100644
--- a/conf/machine/rock-pi-e.conf
+++ b/conf/machine/rock-pi-e.conf
@@ -7,9 +7,7 @@ require conf/machine/include/rk3328.inc
MACHINEOVERRIDES =. "rock-pi-e:"
-PREFERRED_PROVIDER:virtual/kernel = "linux-yocto-dev"
KERNEL_DEVICETREE = "rockchip/rk3328-rock-pi-e.dtb"
MACHINE_EXTRA_RRECOMMENDS += "kernel-modules"
-PREFERRED_PROVIDER:virtual/bootloader = "u-boot"
UBOOT_MACHINE = "rock-pi-e-rk3328_defconfig"
--
2.34.1.75.gabe6bb3905
[meta-rockchip][PATCH] rock-pi-e: override syntax fixup
Trevor Woerner
The _virtual notation is not an override. These syntax "fixes" need to be
reverted.
In the case of the kernel override, when it was added, the rock-pi-e needed
the latest kernel (linux-yocto-dev) but now the default linux-yocto kernel
will suffice. So this mistake actually switched the rock-pi-e from
linux-yocto-dev back to linux-yocto inadvertently but at a time when
linux-yocto-dev was no longer required.
In the case of the bootloader override, u-boot was always the default, so this
override was always redundant.
Therefore, in the end, simply removing both these overrides is the best way
forward.
Signed-off-by: Trevor Woerner <twoerner@...>
---
conf/machine/rock-pi-e.conf | 2 --
1 file changed, 2 deletions(-)
diff --git a/conf/machine/rock-pi-e.conf b/conf/machine/rock-pi-e.conf
index 7f49c9f..0e2856f 100644
--- a/conf/machine/rock-pi-e.conf
+++ b/conf/machine/rock-pi-e.conf
@@ -7,9 +7,7 @@ require conf/machine/include/rk3328.inc
MACHINEOVERRIDES =. "rock-pi-e:"
-PREFERRED_PROVIDER:virtual/kernel = "linux-yocto-dev"
KERNEL_DEVICETREE = "rockchip/rk3328-rock-pi-e.dtb"
MACHINE_EXTRA_RRECOMMENDS += "kernel-modules"
-PREFERRED_PROVIDER:virtual/bootloader = "u-boot"
UBOOT_MACHINE = "rock-pi-e-rk3328_defconfig"
--
2.34.1.75.gabe6bb3905
reverted.
In the case of the kernel override, when it was added, the rock-pi-e needed
the latest kernel (linux-yocto-dev) but now the default linux-yocto kernel
will suffice. So this mistake actually switched the rock-pi-e from
linux-yocto-dev back to linux-yocto inadvertently but at a time when
linux-yocto-dev was no longer required.
In the case of the bootloader override, u-boot was always the default, so this
override was always redundant.
Therefore, in the end, simply removing both these overrides is the best way
forward.
Signed-off-by: Trevor Woerner <twoerner@...>
---
conf/machine/rock-pi-e.conf | 2 --
1 file changed, 2 deletions(-)
diff --git a/conf/machine/rock-pi-e.conf b/conf/machine/rock-pi-e.conf
index 7f49c9f..0e2856f 100644
--- a/conf/machine/rock-pi-e.conf
+++ b/conf/machine/rock-pi-e.conf
@@ -7,9 +7,7 @@ require conf/machine/include/rk3328.inc
MACHINEOVERRIDES =. "rock-pi-e:"
-PREFERRED_PROVIDER:virtual/kernel = "linux-yocto-dev"
KERNEL_DEVICETREE = "rockchip/rk3328-rock-pi-e.dtb"
MACHINE_EXTRA_RRECOMMENDS += "kernel-modules"
-PREFERRED_PROVIDER:virtual/bootloader = "u-boot"
UBOOT_MACHINE = "rock-pi-e-rk3328_defconfig"
--
2.34.1.75.gabe6bb3905
Re: [meta-rockchip][PATCH] trusted-firmware-a: replace baudrate with the one specified in machine conf
Trevor Woerner
On Fri 2021-12-10 @ 03:50:19 PM, Quentin Schulz wrote:
Hi Trevor,Sounds good.
On Fri, Dec 10, 2021 at 09:43:39AM -0500, Trevor Woerner wrote:On Thu 2021-11-11 @ 06:00:02 PM, Quentin Schulz wrote:WouldNot all Rockchip boards have their console running at 1500000 baud inThis looks fragile to me, any change in the number of spaces/tabs and this
U-Boot and the kernel. Such is the case for puma-haikou RK3399-based
SoM+Carrierboard.
In order to prepare for the addition of puma-haikou to meta-rockchip,
let's replace the baudrate in TF-A by the one defined in the machine
conf file in the RK_CONSOLE_BAUD variable.
Cc: Quentin Schulz <foss@...>
Signed-off-by: Quentin Schulz <quentin.schulz@...>
---
.../files/serial-console-baudrate.patch | 36 -------------------
.../trusted-firmware-a_%.bbappend | 7 +++-
2 files changed, 6 insertions(+), 37 deletions(-)
delete mode 100644 recipes-bsp/trusted-firmware-a/files/serial-console-baudrate.patch
diff --git a/recipes-bsp/trusted-firmware-a/files/serial-console-baudrate.patch b/recipes-bsp/trusted-firmware-a/files/serial-console-baudrate.patch
deleted file mode 100644
index 2d6e9bf..0000000
--- a/recipes-bsp/trusted-firmware-a/files/serial-console-baudrate.patch
+++ /dev/null
@@ -1,36 +0,0 @@
-From 840d6b6420e1fd8cdf6e4de7fa58a6f8de151622 Mon Sep 17 00:00:00 2001
-From: Yann Dirson <yann@...>
-Date: Tue, 6 Apr 2021 17:28:45 +0200
-Subject: [PATCH] Set serial console baudrate back to 1500000.
-Upstream-Status: Inappropriate[other]
-
-TF-A runs between two u-boot stages which both uses 1500000 baud, it
-just makes no sense to use the same UART at a different rate.
-
-This effectively reverts part of 0c05748bdebfad9fa43a80962186438bb8fbce62.
-Main reason for that change stated in https://urldefense.proofpoint.com/v2/url?u=https-3A__developer.trustedfirmware.org_T762&d=DwIBaQ&c=_sEr5x9kUWhuk4_nFwjJtA&r=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t&m=TULURVxAXuoOr1qm-lWPJ4RyXC82jen1-RFqhySvz2ZLazQ8DA84GQ7T4MccEcQp&s=7WhFJXuPJAZq8RxczqF3HrMD5JqRZdJ8MyMU9iEnq44&e=
-is ChromeOS compatibility.
-
-Looks like this patch may become unnecessary in the future, when
-u-boot and TF-A get to communicate this value.
-
----
- plat/rockchip/rk3399/rk3399_def.h | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/plat/rockchip/rk3399/rk3399_def.h b/plat/rockchip/rk3399/rk3399_def.h
-index ba83242eb..8d6ecfbe6 100644
---- a/plat/rockchip/rk3399/rk3399_def.h
-+++ b/plat/rockchip/rk3399/rk3399_def.h
-@@ -17,7 +17,7 @@
- /**************************************************************************
- * UART related constants
- **************************************************************************/
--#define RK3399_BAUDRATE 115200
-+#define RK3399_BAUDRATE 1500000
- #define RK3399_UART_CLOCK 24000000
-
- /******************************************************************************
---
-2.30.2
-
diff --git a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend
index f7777a7..0d06c44 100644
--- a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend
+++ b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend
@@ -7,9 +7,14 @@ COMPATIBLE_MACHINE:append:rk3328 = "|rk3328"
FILESEXTRAPATHS:prepend := "${THISDIR}/files:"
SRC_URI += "\
- file://serial-console-baudrate.patch \
file://0001-Fix-build-with-gcc-11.patch \
file://0001-dram-Fix-build-with-gcc-11.patch \
file://0001-plat_macros.S-Use-compatible-.asciz-asm-directive.patch \
file://0001-pmu-Do-not-mark-already-defined-functions-as-weak.patch \
"
+
+fixup_rk3399_baudrate() {
+ sed -i "s/#define RK3399_BAUDRATE 115200/#define RK3399_BAUDRATE ${RK_CONSOLE_BAUD}/" ${S}/plat/rockchip/rk3399/rk3399_def.h
+}
line will stop working. Thankfully the symbol RK3399_BAUDRATE only appears
once in this file! That will allow us to do something like the following
instead:
sed '/RK3399_BAUDRATE.*/RK3399_BAUDRATE ${RK_CONSOLE_BAUD}/d'
sed -i "s/#define RK3399_BAUDRATE\s\+.*/#define RK3399_BAUDRATE plep/" ${S}/plat/rockchip/rk3399/rk3399_def.h
work for you?
This makes sure that only RK3399_BAUDRATE definition will be changed, no
comment, no RK3399_BAUDRATE_OTHER_VAR or RK3399_BAUDRATE being used in
code/other constant in this file.
Re: [meta-rockchip][PATCH] trusted-firmware-a: replace baudrate with the one specified in machine conf
Trevor Woerner
On Thu 2021-11-11 @ 06:00:02 PM, Quentin Schulz wrote:
line will stop working. Thankfully the symbol RK3399_BAUDRATE only appears
once in this file! That will allow us to do something like the following
instead:
sed '/RK3399_BAUDRATE.*/RK3399_BAUDRATE ${RK_CONSOLE_BAUD}/d'
Can you test and submit a v2 please?
Not all Rockchip boards have their console running at 1500000 baud inThis looks fragile to me, any change in the number of spaces/tabs and this
U-Boot and the kernel. Such is the case for puma-haikou RK3399-based
SoM+Carrierboard.
In order to prepare for the addition of puma-haikou to meta-rockchip,
let's replace the baudrate in TF-A by the one defined in the machine
conf file in the RK_CONSOLE_BAUD variable.
Cc: Quentin Schulz <foss@...>
Signed-off-by: Quentin Schulz <quentin.schulz@...>
---
.../files/serial-console-baudrate.patch | 36 -------------------
.../trusted-firmware-a_%.bbappend | 7 +++-
2 files changed, 6 insertions(+), 37 deletions(-)
delete mode 100644 recipes-bsp/trusted-firmware-a/files/serial-console-baudrate.patch
diff --git a/recipes-bsp/trusted-firmware-a/files/serial-console-baudrate.patch b/recipes-bsp/trusted-firmware-a/files/serial-console-baudrate.patch
deleted file mode 100644
index 2d6e9bf..0000000
--- a/recipes-bsp/trusted-firmware-a/files/serial-console-baudrate.patch
+++ /dev/null
@@ -1,36 +0,0 @@
-From 840d6b6420e1fd8cdf6e4de7fa58a6f8de151622 Mon Sep 17 00:00:00 2001
-From: Yann Dirson <yann@...>
-Date: Tue, 6 Apr 2021 17:28:45 +0200
-Subject: [PATCH] Set serial console baudrate back to 1500000.
-Upstream-Status: Inappropriate[other]
-
-TF-A runs between two u-boot stages which both uses 1500000 baud, it
-just makes no sense to use the same UART at a different rate.
-
-This effectively reverts part of 0c05748bdebfad9fa43a80962186438bb8fbce62.
-Main reason for that change stated in https://developer.trustedfirmware.org/T762
-is ChromeOS compatibility.
-
-Looks like this patch may become unnecessary in the future, when
-u-boot and TF-A get to communicate this value.
-
----
- plat/rockchip/rk3399/rk3399_def.h | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/plat/rockchip/rk3399/rk3399_def.h b/plat/rockchip/rk3399/rk3399_def.h
-index ba83242eb..8d6ecfbe6 100644
---- a/plat/rockchip/rk3399/rk3399_def.h
-+++ b/plat/rockchip/rk3399/rk3399_def.h
-@@ -17,7 +17,7 @@
- /**************************************************************************
- * UART related constants
- **************************************************************************/
--#define RK3399_BAUDRATE 115200
-+#define RK3399_BAUDRATE 1500000
- #define RK3399_UART_CLOCK 24000000
-
- /******************************************************************************
---
-2.30.2
-
diff --git a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend
index f7777a7..0d06c44 100644
--- a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend
+++ b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend
@@ -7,9 +7,14 @@ COMPATIBLE_MACHINE:append:rk3328 = "|rk3328"
FILESEXTRAPATHS:prepend := "${THISDIR}/files:"
SRC_URI += "\
- file://serial-console-baudrate.patch \
file://0001-Fix-build-with-gcc-11.patch \
file://0001-dram-Fix-build-with-gcc-11.patch \
file://0001-plat_macros.S-Use-compatible-.asciz-asm-directive.patch \
file://0001-pmu-Do-not-mark-already-defined-functions-as-weak.patch \
"
+
+fixup_rk3399_baudrate() {
+ sed -i "s/#define RK3399_BAUDRATE 115200/#define RK3399_BAUDRATE ${RK_CONSOLE_BAUD}/" ${S}/plat/rockchip/rk3399/rk3399_def.h
+}
line will stop working. Thankfully the symbol RK3399_BAUDRATE only appears
once in this file! That will allow us to do something like the following
instead:
sed '/RK3399_BAUDRATE.*/RK3399_BAUDRATE ${RK_CONSOLE_BAUD}/d'
Can you test and submit a v2 please?
+
+do_patch[postfuncs] += "fixup_rk3399_baudrate"
--
2.30.2
Re: [OE-core] [PATCH] libva: move wayland PACKAGECONFIG to libva.inc
Alexander Kanavin
Please send the patch to openembedded-core list.
Also I wonder about this:
| Run-time dependency wayland-client found: YES 1.19.0
How does it happen? Is something else building wayland items?
Alex
On Fri, 10 Dec 2021 at 06:40, Markus Volk <f_l_k@...> wrote:
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 <f_l_k@...>
---
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
Re: [meta-rockchip][PATCH] trusted-firmware-a: Pin to use gcc for now
Trevor Woerner
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+Applied to meta-rockchip master. Thanks!
it needs looking into, until then use gcc always to build it
Signed-off-by: Khem Raj <raj.khem@...>
Cc: Jon Mason <jon.mason@...>
Cc: Ross Burton <ross.burton@...>
---
.../trusted-firmware-a/trusted-firmware-a_%.bbappend | 7 +++++++
1 file changed, 7 insertions(+)
[OE-core] [PATCH] libva: move wayland PACKAGECONFIG to libva.inc
Markus Volk
I encountered an error while trying to build libva under wayland. libva-i=
nitial
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/cor=
texa72-cortexa53-crypto-poky-linux/libva-initial/2.13.0-r0/build/meson-lo=
gs/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 avai=
lable to libva-initial also
Signed-off-by: MarkusVolk <f_l_k@...>
---
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-graphic=
s/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 =3D "https://github.com/intel/libva=
/releases"
DEPENDS =3D "libdrm"
=20
inherit meson pkgconfig
+
+PACKAGECONFIG:append =3D " \
+ ${@bb.utils.filter('DISTRO_FEATURES', 'wayland', d)} \
+"
+
+PACKAGECONFIG[wayland] =3D "-Dwith_wayland=3Dyes,-Dwith_wayland=3Dno,way=
land-native wayland"
+
diff --git a/meta/recipes-graphics/libva/libva_2.13.0.bb b/meta/recipes-g=
raphics/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
=20
PACKAGECONFIG ??=3D " \
${@bb.utils.contains('DISTRO_FEATURES', 'x11 opengl', 'glx', '', d)}=
\
- ${@bb.utils.filter('DISTRO_FEATURES', 'x11 wayland', d)} \
+ ${@bb.utils.filter('DISTRO_FEATURES', 'x11', d)} \
"
=20
PACKAGECONFIG[x11] =3D "-Dwith_x11=3Dyes,-Dwith_x11=3Dno,virtual/libx11 =
libxext libxfixes"
PACKAGECONFIG[glx] =3D "-Dwith_glx=3Dyes,-Dwith_glx=3Dno,virtual/mesa"
=20
-PACKAGECONFIG[wayland] =3D "-Dwith_wayland=3Dyes,-Dwith_wayland=3Dno,way=
land-native wayland"
-
PACKAGES =3D+ "${PN}-x11 ${PN}-glx ${PN}-wayland"
=20
RDEPENDS:${PN}-x11 =3D+ "${PN}"
--=20
2.25.1
nitial
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/cor=
texa72-cortexa53-crypto-poky-linux/libva-initial/2.13.0-r0/build/meson-lo=
gs/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 avai=
lable to libva-initial also
Signed-off-by: MarkusVolk <f_l_k@...>
---
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-graphic=
s/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 =3D "https://github.com/intel/libva=
/releases"
DEPENDS =3D "libdrm"
=20
inherit meson pkgconfig
+
+PACKAGECONFIG:append =3D " \
+ ${@bb.utils.filter('DISTRO_FEATURES', 'wayland', d)} \
+"
+
+PACKAGECONFIG[wayland] =3D "-Dwith_wayland=3Dyes,-Dwith_wayland=3Dno,way=
land-native wayland"
+
diff --git a/meta/recipes-graphics/libva/libva_2.13.0.bb b/meta/recipes-g=
raphics/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
=20
PACKAGECONFIG ??=3D " \
${@bb.utils.contains('DISTRO_FEATURES', 'x11 opengl', 'glx', '', d)}=
\
- ${@bb.utils.filter('DISTRO_FEATURES', 'x11 wayland', d)} \
+ ${@bb.utils.filter('DISTRO_FEATURES', 'x11', d)} \
"
=20
PACKAGECONFIG[x11] =3D "-Dwith_x11=3Dyes,-Dwith_x11=3Dno,virtual/libx11 =
libxext libxfixes"
PACKAGECONFIG[glx] =3D "-Dwith_glx=3Dyes,-Dwith_glx=3Dno,virtual/mesa"
=20
-PACKAGECONFIG[wayland] =3D "-Dwith_wayland=3Dyes,-Dwith_wayland=3Dno,way=
land-native wayland"
-
PACKAGES =3D+ "${PN}-x11 ${PN}-glx ${PN}-wayland"
=20
RDEPENDS:${PN}-x11 =3D+ "${PN}"
--=20
2.25.1
[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 <raj.khem@...>
Cc: Jon Mason <jon.mason@...>
Cc: Ross Burton <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
it needs looking into, until then use gcc always to build it
Signed-off-by: Khem Raj <raj.khem@...>
Cc: Jon Mason <jon.mason@...>
Cc: Ross Burton <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
Re: standard SDK build with clang compiler built into kernel image
Monsees, Steven C (US)
Thanks again, will take a look and give it a try...
toggle quoted message
Show quoted text
-----Original Message-----
From: Khem Raj <raj.khem@...>
Sent: Thursday, December 9, 2021 2:55 PM
To: Monsees, Steven C (US) <steven.monsees@...>
Cc: yocto@...
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 <steven.monsees=baesystems.com@...> wrote:
From: Khem Raj <raj.khem@...>
Sent: Thursday, December 9, 2021 2:55 PM
To: Monsees, Steven C (US) <steven.monsees@...>
Cc: yocto@...
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 <steven.monsees=baesystems.com@...> 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, 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 /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-undname, 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-mt, 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, 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-extract, 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-jitlink, 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/modularize, 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-opt-report, 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/bugpoint, 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/lld, 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/dsymutil, 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-dwp, 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-cat, 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-dis, 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-c-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-refactor, 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/sanstats, 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-size, 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/yaml2obj, 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-split, 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-rename, 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-vscode, 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-readobj, 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-tblgen, 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-argdumper, 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-check, 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-xray, 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/clangd, 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-scan-deps, 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-rc, 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-lto, 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-mi, 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-modextract, 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-rtdyld, 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-diff, 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-change-namespace, 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-cfi-verify, 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-query, 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-link, 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-offload-bundler, 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-import-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-format, 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-include-fixer, 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/diagtool, 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/sancov, 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-objcopy, 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-cxxmap, 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-strings, 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-lto2, 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/llc, 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/opt, 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-exegesis, 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-spirv, 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-cvtres, 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-cov, 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-lipo, 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/find-all-symbols, 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/obj2yaml, 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/verify-uselistorder, 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-objdump, 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-mc, 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/lli, 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-config, 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-stress, 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-server, 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-cxxfilt, 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-profdata, 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-pdbutil, 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-bcanalyzer, 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-tblgen, 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-nm, 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/lib/liblldbIntelFeatures.so.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/lib/libRemarks.so.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/lib/libclang.so.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/lib/liblldb.so.9.0.1, 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/lib/libclang-cpp.so.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/lib/LLVMgold.so, 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/lib/libLTO.so.9, interp size = 72 and 95 is needed.
done
SDK has been successfully set up and is ready to be used.
Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g.
$ .
/disk0/scratch/smonsees/yocto/sdk_3.0.4/environment-setup-corei7-64-po
ky-linux
-bash-4.2$
Thanks,
Steve
Re: 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
<steven.monsees=baesystems.com@...> wrote:
toggle quoted message
Show quoted text
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
<steven.monsees=baesystems.com@...> 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 /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 /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-undname, 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-mt, 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, 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-extract, 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-jitlink, 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/modularize, 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-opt-report, 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/bugpoint, 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/lld, 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/dsymutil, 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-dwp, 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-cat, 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-dis, 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-c-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-refactor, 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/sanstats, 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-size, 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/yaml2obj, 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-split, 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-rename, 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-vscode, 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-readobj, 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-tblgen, 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-argdumper, 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-check, 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-xray, 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/clangd, 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-scan-deps, 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-rc, 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-lto, 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-mi, 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-modextract, 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-rtdyld, 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-diff, 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-change-namespace, 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-cfi-verify, 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-query, 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-link, 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-offload-bundler, 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-import-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-format, 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-include-fixer, 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/diagtool, 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/sancov, 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-objcopy, 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-cxxmap, 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-strings, 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-lto2, 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/llc, 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/opt, 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-exegesis, 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-spirv, 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-cvtres, 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-cov, 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-lipo, 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/find-all-symbols, 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/obj2yaml, 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/verify-uselistorder, 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-objdump, 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-mc, 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/lli, 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-config, 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-stress, 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-server, 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-cxxfilt, 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-profdata, 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-pdbutil, 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-bcanalyzer, 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-tblgen, 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-nm, 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/lib/liblldbIntelFeatures.so.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/lib/libRemarks.so.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/lib/libclang.so.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/lib/liblldb.so.9.0.1, 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/lib/libclang-cpp.so.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/lib/LLVMgold.so, 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/lib/libLTO.so.9, interp size = 72 and 95 is needed.
done
SDK has been successfully set up and is ready to be used.
Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g.
$ . /disk0/scratch/smonsees/yocto/sdk_3.0.4/environment-setup-corei7-64-poky-linux
-bash-4.2$
Thanks,
Steve
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] <vmeson> Agenda Items?
[09:01] <vmeson> 1. PSI /proc/pressure
see: https://www.kernel.org/doc/html/latest/accounting/psi.html
[09:01] <vmeson> 2. Status of AB
[09:02] <vmeson> 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] <vmeson> read-only YP BZ database query to find "AB-INT" build failures, find build and highlight in "non-release" AB build summary.
[09:23] <vmeson> add /proc/pressure info to test results logs.
Sakib and I may do this, else Alex in January
[09:24] <vmeson> network access: weird AB bugs: DNS or connextion failure, at times even qemu net connection fails!
[09:26] <vmeson> 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] <vmeson> Test system, start / stop qemu instances in a loop.
[09:29] <vmeson> 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] <abelloni> vmeson: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14467
[09:32] <vmeson> use rest API to query the bugzilla -- where's the API?
[09:33] <abelloni> https://wiki.mozilla.org/Bugzilla:REST_API
[09:33] <abelloni> I'll have a look at that
[09:37] <RP> "BzAPI is an alternate, deprecated REST API" - that will be ours as we're not on bz5 yet
Notes from previous meeting which are largely still relevant.
1. job server
- ninja could be patched with make's more responsive algorithm
next or is this good enough?
Aug 26:
Randy made some graphs that show that the -l NUM results
in the number of compile jobs oscillates *wildly* between 0 and 200
on a 192 core builder compiling chromium. What I did was:
$ bitbake -c cleansstate chromium-x11
$ bitbake -c configure chromium-x11
$ bitbake -c compile chromium-x11
and while that compile was running:
$ while [ ! -f /tmp/compiling-chromium-is-done ]; do \
cat /proc/loadavg >> procs-load.log ; sleep 0.5 ;
done
Results so far:
https://postimg.cc/gallery/3hjfYfG/f8f46c97
Next step is either:
a. collect data as above for an image build and see if the sub-optimal
ninja behaviour makes a difference
and/or
b. patch ninja with make's more responsive load avg
algorithm:
https://git.savannah.gnu.org/cgit/make.git/commit/?id=d8728efc8
- Richard suggested that we extract make's code for measuring the load
average to a separate binary and run it in the periodic io latency
test. Also can we translate it to python?
- Trevor is working on this and had some problems so next week.
(Aug 19 - Trevor is back from vaction so maybe next week.)
- Trevor to see if the load average change really did reduce load
on WR build systems. (Aug 19)
2. AB status
Trevor is learning about buildbot and working on a scheduling bug
(CentOS worker?)
bitbake layer setup tool should allow multiple backends:
eg: kas, a y-a-helper.
ptest cases are improving, we may be close to done!
Let's wait a week to see how things go.
(July29, Aug 5, Aug 19, we're not done...)
- lttng-tools ptest is failing. RP is working on it with upstream.
The timeout (done on Aug 5) increase hasn't helped.
3. Sakib's improvements to the logging are merged.
Sakib generated a summary of all high latency 'top' logs from
~July 23->July 29 by just running his summary script on the
merged raw top logs.
More analysis required....
Still relevant parts of
Previous Meeting Notes:
=======================
4. bitbake server timeout ( no change july 29, Aug 19, Oct 7)
"Timeout while waiting for a reply from the bitbake server (60s)"
5. io stalls (no update: July 29, Oct 7)
Richard said that it would make sense to write an ftrace utility
/ script to monitor io latency and we could install it with sudo
Ch^W mentioned ftrace on IRC.
Sakib and Randy will work on that but not for a week or two
or longer! (Aug 19).
Randy collected iostat data on 3 build server:
https://postimg.cc/gallery/8cN6LYB
We agreed that having -ty-2 be ~ 100 utilization for many hours
in a row is not acceptable and that a threshold of ~ 10 minutes
at 100% utilization may be a reasonable limt. I need to figure out
if I can get data on the fraction of IO done per IO clas since
we do use ionice to do clean-up and other activities.
../Randy
===================================
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] <vmeson> Agenda Items?
[09:01] <vmeson> 1. PSI /proc/pressure
see: https://www.kernel.org/doc/html/latest/accounting/psi.html
[09:01] <vmeson> 2. Status of AB
[09:02] <vmeson> 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] <vmeson> read-only YP BZ database query to find "AB-INT" build failures, find build and highlight in "non-release" AB build summary.
[09:23] <vmeson> add /proc/pressure info to test results logs.
Sakib and I may do this, else Alex in January
[09:24] <vmeson> network access: weird AB bugs: DNS or connextion failure, at times even qemu net connection fails!
[09:26] <vmeson> 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] <vmeson> Test system, start / stop qemu instances in a loop.
[09:29] <vmeson> 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] <abelloni> vmeson: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14467
[09:32] <vmeson> use rest API to query the bugzilla -- where's the API?
[09:33] <abelloni> https://wiki.mozilla.org/Bugzilla:REST_API
[09:33] <abelloni> I'll have a look at that
[09:37] <RP> "BzAPI is an alternate, deprecated REST API" - that will be ours as we're not on bz5 yet
Notes from previous meeting which are largely still relevant.
1. job server
- ninja could be patched with make's more responsive algorithm
next or is this good enough?
Aug 26:
Randy made some graphs that show that the -l NUM results
in the number of compile jobs oscillates *wildly* between 0 and 200
on a 192 core builder compiling chromium. What I did was:
$ bitbake -c cleansstate chromium-x11
$ bitbake -c configure chromium-x11
$ bitbake -c compile chromium-x11
and while that compile was running:
$ while [ ! -f /tmp/compiling-chromium-is-done ]; do \
cat /proc/loadavg >> procs-load.log ; sleep 0.5 ;
done
Results so far:
https://postimg.cc/gallery/3hjfYfG/f8f46c97
Next step is either:
a. collect data as above for an image build and see if the sub-optimal
ninja behaviour makes a difference
and/or
b. patch ninja with make's more responsive load avg
algorithm:
https://git.savannah.gnu.org/cgit/make.git/commit/?id=d8728efc8
- Richard suggested that we extract make's code for measuring the load
average to a separate binary and run it in the periodic io latency
test. Also can we translate it to python?
- Trevor is working on this and had some problems so next week.
(Aug 19 - Trevor is back from vaction so maybe next week.)
- Trevor to see if the load average change really did reduce load
on WR build systems. (Aug 19)
2. AB status
Trevor is learning about buildbot and working on a scheduling bug
(CentOS worker?)
bitbake layer setup tool should allow multiple backends:
eg: kas, a y-a-helper.
ptest cases are improving, we may be close to done!
Let's wait a week to see how things go.
(July29, Aug 5, Aug 19, we're not done...)
- lttng-tools ptest is failing. RP is working on it with upstream.
The timeout (done on Aug 5) increase hasn't helped.
3. Sakib's improvements to the logging are merged.
Sakib generated a summary of all high latency 'top' logs from
~July 23->July 29 by just running his summary script on the
merged raw top logs.
More analysis required....
Still relevant parts of
Previous Meeting Notes:
=======================
4. bitbake server timeout ( no change july 29, Aug 19, Oct 7)
"Timeout while waiting for a reply from the bitbake server (60s)"
5. io stalls (no update: July 29, Oct 7)
Richard said that it would make sense to write an ftrace utility
/ script to monitor io latency and we could install it with sudo
Ch^W mentioned ftrace on IRC.
Sakib and Randy will work on that but not for a week or two
or longer! (Aug 19).
Randy collected iostat data on 3 build server:
https://postimg.cc/gallery/8cN6LYB
We agreed that having -ty-2 be ~ 100 utilization for many hours
in a row is not acceptable and that a threshold of ~ 10 minutes
at 100% utilization may be a reasonable limt. I need to figure out
if I can get data on the fraction of IO done per IO clas since
we do use ionice to do clean-up and other activities.
../Randy
standard SDK build with clang compiler built into kernel image
Monsees, Steven C (US)
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 /disk0/scratch/smonsees/yocto/sdk_3.0.4/sysroots/x86_64-pokysdk-linux/usr/bin/llvm-undname, 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-mt, 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, 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-extract, 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-jitlink, 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/modularize, 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-opt-report, 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/bugpoint, 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/lld, 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/dsymutil, 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-dwp, 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-cat, 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-dis, 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-c-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-refactor, 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/sanstats, 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-size, 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/yaml2obj, 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-split, 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-rename, 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-vscode, 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-readobj, 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-tblgen, 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-argdumper, 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-check, 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-xray, 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/clangd, 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-scan-deps, 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-rc, 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-lto, 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-mi, 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-modextract, 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-rtdyld, 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-diff, 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-change-namespace, 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-cfi-verify, 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-query, 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-link, 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-offload-bundler, 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-import-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-format, 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-include-fixer, 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/diagtool, 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/sancov, 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-objcopy, 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-cxxmap, 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-strings, 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-lto2, 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/llc, 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/opt, 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-exegesis, 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-spirv, 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-cvtres, 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-cov, 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-lipo, 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/find-all-symbols, 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/obj2yaml, 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/verify-uselistorder, 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-objdump, 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-mc, 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/lli, 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-config, 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-stress, 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-server, 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-cxxfilt, 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-profdata, 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-pdbutil, 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-bcanalyzer, 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-tblgen, 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-nm, 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/lib/liblldbIntelFeatures.so.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/lib/libRemarks.so.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/lib/libclang.so.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/lib/liblldb.so.9.0.1, 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/lib/libclang-cpp.so.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/lib/LLVMgold.so, 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/lib/libLTO.so.9, interp size = 72 and 95 is needed.
done
SDK has been successfully set up and is ready to be used.
Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g.
$ . /disk0/scratch/smonsees/yocto/sdk_3.0.4/environment-setup-corei7-64-poky-linux
-bash-4.2$
Thanks,
Steve
Re: honister - errors while patching net-snmp 5.9
On Thu, Dec 9, 2021 at 7:59 AM Ori Pessach <mail@...> wrote:
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 ?
The changes are the same as master and it applies fine on master
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.
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
Specify systemd startup order for volatile-bind and network setup
Silvan Murer
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
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
Minutes: Yocto Project Weekly Triage Meeting 12/9/2021
Trevor Gamblin
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)
AB Bugs: 67
(Last week 61)
honister - errors while patching net-snmp 5.9
Ori Pessach
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
kwayland-server-5.23.1
sateesh m
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.
--
Regards,
Sateesh
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
netkit-ftp for yocto
lavkhush2208@...
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&R
lavkhush
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&R
lavkhush
Re: [meta-raspberrypi][PATCH] xserver-xorg: remove xshmfence configure option
On Wed, Dec 8, 2021 at 7:03 PM Yu, Mingli <mingli.yu@...> wrote:
From: Mingli Yu <mingli.yu@...>
After the commit [1] introduced in openembedded-core layer,
some configure options is't carried over include xshmfence
option, so remove the xshmfence configure option to silence
the below warning.
WARNING: xserver-xorg-2_21.1.1-r0 do_configure: QA Issue: xserver-xorg: invalid PACKAGECONFIG: xshmfence [invalid-packageconfig]
That’s ok to remove it but more importantly does it work now without this option
[1] https://git.openembedded.org/openembedded-core/commit/?id=e05abd87ee5d23750c641d0129d9c83db68ee2e8
Signed-off-by: Mingli Yu <mingli.yu@...>
---
recipes-graphics/xorg-xserver/xserver-xorg_%.bbappend | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-graphics/xorg-xserver/xserver-xorg_%.bbappend b/recipes-graphics/xorg-xserver/xserver-xorg_%.bbappend
index 25829c2..ee4812f 100644
--- a/recipes-graphics/xorg-xserver/xserver-xorg_%.bbappend
+++ b/recipes-graphics/xorg-xserver/xserver-xorg_%.bbappend
@@ -1,4 +1,4 @@
-OPENGL_PKGCONFIGS:rpi = "dri glx ${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', 'dri3 xshmfence glamor', '', d)}"
+OPENGL_PKGCONFIGS:rpi = "dri glx ${@bb.utils.contains('MACHINE_FEATURES', 'vc4graphics', 'dri3 glamor', '', d)}"
# when using userland graphic KHR/khrplatform.h is provided by userland but virtual/libgl is provided by mesa-gl where
# we explicitly delete KHR/khrplatform.h since its already coming from userland package
--
2.17.1