Re: [yocto] Correct way for multiple recipes to install files in the same directory

On Fri, Apr 12 2024 at 09:14:45 AM -07:00:00, Linus Nilsson wrote: I haven't worked with the classes yet but I can see how they can be used to make things a lot easier in my case. But don't use classen too invasively. They can be problematic, e.g. an :append may be ignored depending on the

Re: [yocto] Correct way for multiple recipes to install files in the same directory

On Thu, Apr 11 2024 at 12:52:49 AM -07:00:00, linusnils...@hotmail.com wrote: Is there a proper way to do this? Kind regards, Linus Hi, can't tell if this would be a proper way, but this is how I do it and what works for me: Create a main user:

Re: [yocto] Yocto Project Quick Build - MACHINE

On Thu, Mar 7 2024 at 03:46:30 PM -08:00:00, Worik Stanton wrote: What have I done wrong? Hi, did you add meta-altera here? build/conf/bblayers.conf -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62704):

Re: [yocto] Building Tailscale with Yocto #golang

On Mon, Jul 3 2023 at 09:07:11 AM -0400, Bruce Ashfield wrote: We really shouldn't suggest the above to a developer without also the explanation as to why network access is disabled by default in tasks such as compile. You are of course right with your objections. However, this is the only

Re: [yocto] Building Tailscale with Yocto #golang

You need to allow network connection for the do_compile task do_compile[network] = "1" On Sun, Jul 2 2023 at 12:45:40 PM -0700, przemek.re...@gmail.com wrote: Hi! I'm trying to build Tailscale with Yocto This is me recipe: inherit go-mod SRC_URI =

Re: [yocto] [meta-raspberrypi] vc4-fkms-v3d vs. vc4-kms-v3d

On Sun, Jun 25 2023 at 12:01:29 AM +0200, Manuel Wagesreither wrote: The HDMI port is unused on my raspi. I'm using the official Raspberry Pi 7" Touchscreen connected via DSI. Have you also added ? dtoverlay=vc4-kms-dsi-7inch dtoverlay=rpi-ft5406 I never dealt with the 7'' Display but i

Re: [yocto] [meta-raspberrypi] vc4-fkms-v3d vs. vc4-kms-v3d

Two pitfalls come to mind here It used to be necessary to use vc4-kms-v3d-pi4 dtbo. At some point this was changed so that even for the rpi4 only vc4-kms-v3d overlay had to be loaded and vc4-kms-v3d-pi4 was automatically reloaded. If your software version is old enough, using vc4-kms-v3d-pi4

Re: [yocto] resize2fs, what's provide this package

Hi, you need to install 'e2fsprogs-resize2fs' Am Di, 21. Feb 2023 um 13:02:56 -0800 schrieb Martin Leduc via lists.yoctoproject.org : Hi community, I look for the resize2fs recipes. This application shall be included in the e2fsprog package but it's not there. I've also tried to

Re: [yocto] Hardware accelerated video decoding and display on AMD hardware?

You need to enable gallium-llvm and r600 PACKAGECONFIGS for mesa to build the radeonsi driver On Sat, Jan 28 2023 at 08:07:28 PM -0700, Ori Pessach wrote: Thanks. Unfortunately, neither xf86-video-amdgpu nor linux-firmware seem to be available. meta-amd certainly doesn't have them, and

Re: [yocto] recipe won't build, missing pseudo

Am Mo, 26. Dez 2022 um 18:54:01 -0800 schrieb Mistyron : Hi, I'm want to write a recipe to compile phytool but I'm getting the below error when building it with: $ bitbake -b phytool_2.0

Re: [yocto] lsusb

Am Sa, 24. Dez 2022 um 08:34:49 -0800 schrieb Mistyron : $ grep usb path/to/package.manifest libusb-1.0-0 usbutils usbutils-python lsusb is part of usbutils, so it is not explicitly listed, but should be included in your image -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages

Re: [yocto] undefined reference problem persists

Am So, 6. Nov 2022 um 00:45:36 -0700 schrieb Mistyron : | /usr/src/debug/lrd-networkmanager-sterling/10.4.0.10-r0/build/../lrd-network-manager-10.4.0.10/src/nmcli/common.c:904: undefined reference to `rl_echo_signal_char' missing readline dependency ? -=-=-=-=-=-=-=-=-=-=-=- Links: You

Re: [yocto] Adding Vulkan to core-image-weston

Am Mo, 19. Sep 2022 um 16:54:52 + schrieb Edgar Mobile : This wasn't enough i guess you would also need to add venus support to virglrenderer.bb for qemu: DEPENDS:append = "vulkan-loader vulkan-headers" EXTRA_OEMESON += "-Dvenus-experimental=true" but i have never tested this

Re: [yocto] Adding Vulkan to core-image-weston

Am Mo, 19. Sep 2022 um 16:33:11 +0100 schrieb Alexander Kanavin : You need to check the Mesa recipe to see how the build options are defined mesa builds vulkan support, if you add 'vulkan' to DISTRO_FEATURES. If you need to, you can add additional drivers with a line like this to a

Re: [yocto] wget - The certificate has not yet been activated

Hi Matthias, check if busybox is built with this option CONFIG_FEATURE_WGET_OPENSSL=y On Thu, Feb 3 2022 at 06:37:01 AM +, Matthias Klein wrote: Hello, I have with the current master branch in a IMX6 Yocto the problem that with wget no HTTPS downloads work: # wget -4

Re: [yocto] /bin/sh: 1: bison: not found while compiling own kernel module with poky-dunfell #bitbake

hello, try to add 'bison-native' to DEPENDS. Am 29.12.21 um 07:16 schrieb prashantsi...@dialtronics.com: hello team, I'm trying to build my own kernel module with yocto for raspberry-pi kernel, but it's giving me error that "*bison not found*", as- DEBUG: Executing shell function do_compile

[yocto] [OE-core] [PATCH] libva: move wayland PACKAGECONFIG to libva.inc

I encountered an error while trying to build libva under wayland. libva-initial was missing wayland-native dependency and failed like this: | Run-time dependency xfixes found: NO (tried pkgconfig and cmake) | Run-time dependency wayland-client found: YES 1.19.0 | Program wayland-scanner

[yocto][meta-rockchip][PATCH] rockchip.wks: use uuid for /boot during fstab-update

Since the recent patch to switch to UUIDs [0aa5e600: "use uuid instead of hard-coding root device"] wic fstab-update is not able to get the correct value for the used device anymore and falls to the default 'sda'. Thus wrong /dev/sda entries are generated in fstab. For partitions that should be

[yocto] [meta-rockchip][PATCH] use uuid instead of hard-coding root device

Am 25.09.21 um 17:09 schrieb Trevor Woerner: You'll need to re-send this with a better subject line and commit message so the right people will notice it. Otherwise they'll think it's meta-rockchip-specific. If (when) this patch gets applied upstream, then we can remove our work-around. The

Re: [yocto] [meta-rockchip][PATCH] use uuid instead of hard-coding root device

Am 23.09.21 um 22:55 schrieb Trevor Woerner: We can add the --use-uuid line to the /boot entry if you really think it should be mounted on boot, but we shouldn't use it on the others and cause wic to generate a bad fstab. There are examples of other boards that don't mount /boot by default

Re: [yocto][meta-rockchip][PATCH v2 2/2] rockchip-wic.inc: dont let wic edit fstab by default

Am 24.09.21 um 15:10 schrieb Trevor Woerner: Thanks for the patch and the SoB line. I'm going to apply this patch, but I'm going to amend the commit message to capture some of the conversation we've had. There's a chance we'll want to know "why" at some point in the future ;-) Thanks for

Re: [yocto] [meta-rockchip][PATCH] use uuid instead of hard-coding root device

Am 24.09.21 um 06:46 schrieb Khem Raj: are you both using systemd or sysvinit I am using systemd -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#54841): https://lists.yoctoproject.org/g/yocto/message/54841 Mute This Topic:

Re: [yocto] [meta-rockchip][PATCH] use uuid instead of hard-coding root device

I'm surprised mount doesn't complain about those first 5 lines! Those are not properly-formed fstab(5) entries. No, it doesn't. Those entries are ignored except /boot. One interesting thing: i always had that bunch of malformed fstab entries. Before the change from static to uuid it looked like

[yocto][meta-rockchip][PATCH v2 1/2] rockchip.wks: use uuid for all partitions

My rock pi 4 refused to boot with the latest changes because there are false entries written to fstab. Fix this by using uuid for all partitions Signed-off-by: MarkusVolk --- wic/rockchip.wks | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/wic/rockchip.wks

[yocto][meta-rockchip][PATCH v2 2/2] rockchip-wic.inc: dont let wic edit fstab by default

Signed-off-by: MarkusVolk --- conf/machine/include/rockchip-wic.inc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/conf/machine/include/rockchip-wic.inc b/conf/machine/include/rockchip-wic.inc index 15010a0..30b0d57 100644 --- a/conf/machine/include/rockchip-wic.inc +++

Re: [yocto] [meta-rockchip][PATCH] use uuid instead of hard-coding root device

Am 23.09.21 um 13:59 schrieb Trevor Woerner: Curious. I boot tested my patch on multiple boards and I've built and booted numerous images on my rock-pi-4b and rock64 boards in the last day or so since I applied the patch. I'll try some "clean" builds and see if that makes a difference. I don't

[yocto] [meta-rockchip][PATCH 1/2] rockchip.wks: use uuid for all partitions

My rock pi 4 refused to boot with the latest changes because there are false entries written to fstab. Fix this by using uuid for all partitions --- wic/rockchip.wks | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/wic/rockchip.wks b/wic/rockchip.wks index

[yocto] [meta-rockchip][PATCH 2/2] rockchip-wic.inc: dont let wic edit fstab by default

--- conf/machine/include/rockchip-wic.inc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/conf/machine/include/rockchip-wic.inc b/conf/machine/include/rockchip-wic.inc index 15010a0..30b0d57 100644 --- a/conf/machine/include/rockchip-wic.inc +++ b/conf/machine/include/rockchip-wic.inc @@

Re: [yocto] [meta-rockchip][PATCH] use uuid instead of hard-coding root device

Hi, with this change my rock-pi-4 doesnt boot up and falls to emergency shell because wic includes wrong devices into fstab. For some reason it assumes /dev/sda1. I was able to fix this for my machine by using uuid for all partitions. diff --git a/wic/rockchip.wks b/wic/rockchip.wks index

Re: [yocto] editing Makefile after configure stage to disable -Werror

you could try to add a line like this to your recipe: CFLAGS:append = " -Wno-error=missing-attributes" Am 31.08.21 um 08:41 schrieb Ivan Riabtsov: Hello, I have the following error: ../../elfutils-0.166/libelf/libelfP.h:53:30: error: ‘__elf64_msize’ specifies less restrictive attribute than

Re: [yocto] extrausers-bbclass: plaintext password (since shadow update to 4.9)

I also have problems with setting passwords in current master branch. I only can provide a hacky workaround. I added the following lines to my image recipe to inject the passwords manually after rootfs creation: RETRO_USER_PASSWORD ?= "retro" ROOT_USER_PASSWORD ?= "root"

Re: [yocto] [meta-rockchip] Question about OVERRIDES in meta-rockchip

Learned something new today :) It could be done in local.conf like this: OVERRIDES .= "${@bb.utils.contains_any('SOC_FAMILY', 'rk3066 rk3188 rk3288 rk3399', ':rockchip', '', d)}" DISTRO_FEATURES_remove_rockchip = -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group.

[yocto] [meta-rockchip] Question about OVERRIDES in meta-rockchip

.= ":rockchip" Kind regards, Markus Volk -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#52200): https://lists.yoctoproject.org/g/yocto/message/52200 Mute This Topic: https://lists.yoctoproject.org/mt/80347254/21656 Group Owner

Re: [yocto] rebuild issues using sstate mirror

I sent patches to openembedded-c...@lists.openembedded.org -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#51956): https://lists.yoctoproject.org/g/yocto/message/51956 Mute This Topic: https://lists.yoctoproject.org/mt/79521373/21656 Group Owner:

[yocto] rebuild issues using sstate mirror

Hi Folks, i did some research on building a custom yocto image using gatesgarth branch. The testcase was building an image on one machine and rebuild it on another using sstate mirror. I encountered two issues witch i was able to fix in a way that may also be interesting upstream. The first

[yocto] build issues using sstate mirror

Hi Folks, i did some research on building a custom yocto image using gatesgarth branch. The testcase was building an image on one machine and rebuild it on another using sstate mirror. I encountered two issues which i was able to fix in a way that may also be interesting upstream. The first