That's right, -L is needed. Alex

Hi, I have just completed a bringup of Poky on the ODROID N2+ platform, but noticed that Docker failed to start, complaining that it could not load the "nf_conntrack_netlink" module. After checking

Since that build directory contains symlinks, we may need something like cp -L here? I didn't test but I think we might run into an issue? Cheers, Richard

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Steve, Randy, Bruce, Ross, Richard, Alexandre, Tim, Joshua, Kiran ARs: NONE Notes: NONE

FVP-Base is a better supported and more generally useful machine than N1S= DP. Signed-off-by: Ross Burton <ross.burton@...> --- config.json | 4 +++- 1 file changed, 3 insertions(+), 1

Thank you. I will most likely look into creating a dunfell based build this weekend... My current system is zeus based, centos, still using sysvinit on startup... Did run using clang 9.0 ? I

From: Kai Kang <kai.kang@...> It packages all file in ${libdir} to package sssd, including the .so symlink files. Then it causes QA issues: | ERROR: QA Issue: sssd rdepends on dbus-dev

From: Kai Kang <kai.kang@...> v2: * replace _ with - new sub-package name * allow empty for new sub-package that it is enabled/disabled by a package config Kai Kang (1): sssd:

Progress bar can overlap with products logos, added --disable-progress-bar configure option to disable progress bar completely without patching the code. Default behaviour is to show progress

From: Pavel Zhukov <pavel.zhukov@...> Progress bar can overlap with products logos, added --disable-progress-bar configure option to disable progress bar completely without patching the

On 10/14/21 4:08 AM, akuster808 wrote: Hi armin, > changing the 'libsss_sudo' to 'libsss-sudo' fixes the errors. > > I can do this locally or you can send a v2. v2 will be sent. Thanks. Kai > > -

There are no patches needed other than what is already in oe-core/meta- intel/meta-clang. I tried building zeus on Ubuntu 16.04 and didn't see any problem. zeus is no longer maintained or supported

I have successfully gotten yocto to build the USBIP-tools directory by adding a bb recipe for it, see below. However, I am sure that I have violated ever good and reasonable best practice! Therefore I

Fixes: error in fail2ban setup command: use_2to3 is invalid. ERROR: 'python3 setup.py build ' execution failed. drop custom fail2ban_setup.py remove pyhton-fail2ban as its a symlink to

If you switch to master, it's best if you make a new build directory and dont reuse the one you have. Alex

`export DISPLAY=:0` did the trick. The following shows when still on poky dunfell: * I can now boot `runqmu kvm slirp sdl core-image-weston`. But gui is still slow. I cannot even type `systemctl

changing the 'libsss_sudo' to 'libsss-sudo' fixes the errors. I can do this locally or you can send a v2. - armin

When building for ipk and deb I am seeing these errors. IPK: ERROR: sssd-2.5.2-r0 do_package_write_ipk: Fatal errors occurred

Can you check with current master (instead of dunfell) please? You also need to run runqemu inside an X session (e.g. DISPLAY environment variable should be set to a valid X server). If sdl does not

Hi Alex, Am Fr, 8. Okt 2021, um 11:00, schrieb Alexander Kanavin: Interesting. Things don't work on both my Debian Buster machines. How does opengl get set in qemu-system-native? Am Yocto novice and