While building frr package, we can see errors like below /home/pokybuild/yocto-worker/meta-oe/build/build/tmp/work/core2-64-poky-linux/frr/10.1/recipe-sysroot-native/usr/lib/clippy ./python/clidef.py -o lib/affinitymap_cli_clippy.c lib/affinitymap_cli.c ... /home/pokybuild/yocto-worker/meta-oe/build/build/tmp/work/core2-64-poky-linux/frr/10.1/recipe-sysroot-native/usr/lib/clippy: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory make[1]: *** [Makefile:18452: lib/affinitymap_cli_clippy.c] Error 127 clippy is built by frr-native, however the problem above seems to be that its built on a build host where libatomics.so is present and here its reused via sstate and executing on a host where it is not present. Its seen on alma8-ty-1 build node on AB
Has this happened again Khem? Is is reproducible?
(In reply to Randy MacLeod from comment #1) > Has this happened again Khem? > Is is reproducible? yes it is reproducible. Build frr-native on a build machine with libatomic.so installed. Then build frr on a machine without libatomic.so ( newer distros ) make sure that sstate is shared between these two machines.
(In reply to Randy MacLeod from comment #1) > Has this happened again Khem? > Is is reproducible? saw this today on rocky9-vk-2 https://autobuilder.yoctoproject.org/valkyrie/#/builders/81/builds/415
Any news Khem?
No info, reopen if info becomes available.
We need someone to test "Build frr-native on a build machine with libatomic.so installed. Then build frr on a machine without libatomic.so ( newer distros ) make sure that sstate is shared between these two machines."