Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/o… Package network:osmocom:nightly/osmo-pcu failed to build in openSUSE_Leap_15.1_ARM/aarch64 Check out the package for editing: osc checkout network:osmocom:nightly osmo-pcu Last lines of build log: [ 33s] checking if g++ supports -c -o file.o... yes [ 33s] checking if g++ supports -c -o file.o... (cached) yes [ 33s] checking whether the g++ linker (/usr/aarch64-suse-linux/bin/ld) supports shared libraries... yes [ 33s] checking dynamic linker characteristics... (cached) GNU/Linux ld.so [ 33s] checking how to hardcode library paths into programs... immediate [ 33s] checking for pkg-config... /usr/bin/pkg-config [ 33s] checking for aarch64-suse-linux-gnu-pkg-config... /usr/bin/aarch64-suse-linux-gnu-pkg-config [ 33s] checking pkg-config is at least version 0.20... yes [ 33s] checking for ANSI C header files... (cached) yes [ 33s] checking for libosmocore >= 1.6.0... no [ 33s] configure: error: Package requirements (libosmocore >= 1.6.0) were not met: [ 33s] [ 33s] Package 'libsctp', required by 'libosmocore', not found [ 33s] [ 33s] Consider adjusting the PKG_CONFIG_PATH environment variable if you [ 33s] installed software in a non-standard prefix. [ 33s] [ 33s] Alternatively, you may set the environment variables LIBOSMOCORE_CFLAGS [ 33s] and LIBOSMOCORE_LIBS to avoid the need to call pkg-config. [ 33s] See the pkg-config man page for more details. [ 33s] error: Bad exit status from /var/tmp/rpm-tmp.SFEj3Q (%build) [ 33s] [ 33s] [ 33s] RPM build errors: [ 33s] Bad exit status from /var/tmp/rpm-tmp.SFEj3Q (%build) [ 33s] ### VM INTERACTION START ### [ 35s] [ 28.440967] sysrq: SysRq : Power Off [ 35s] [ 28.441565] reboot: Power down [ 35s] ### VM INTERACTION END ### -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)