On Fri, Jun 11, 2021 at 1:23 PM Geyslan G. Bem <geyslan@xxxxxxxxx> wrote: > > Trying to run vmtest.sh from the bpf-next linux > tools/testing/selftests/bpf on Arch Linux raises this error: > > ./test_progs > ./test_progs: /usr/lib/libc.so.6: version `GLIBC_2.33' not found > (required by ./test_progs) > > VM: > https://libbpf-vmtest.s3-us-west-1.amazonaws.com/x86_64/libbpf-vmtest-rootfs-2020.09.27.tar.zst > > [root@(none) /]# strings /usr/lib/libc.so.6 | grep '^GLIBC_2.' | tail > GLIBC_2.30 > GLIBC_2.5 > GLIBC_2.9 > GLIBC_2.7 > GLIBC_2.6 > GLIBC_2.18 > GLIBC_2.11 > GLIBC_2.16 > GLIBC_2.13 > GLIBC_2.2.6 > > It would be nice to have > https://github.com/libbpf/libbpf/blob/master/travis-ci/vmtest/configs/INDEX > updated to refer to a new image with GLIBC_2.33. > > Host settings: > > $ strings /usr/lib/libc.so.6 | grep GLIBC_2.33 > GLIBC_2.33 > GLIBC_2.33 > It seems kind of silly to update our perfectly working image just because a new version of glibc was released. Is there any way for you to down-grade glibc or build it in some compatibility mode, etc? selftests don't really rely on any bleeding-edge features of glibc. > $ uname -a > Linux hb 5.12.9-arch1-1 #1 SMP PREEMPT Thu, 03 Jun 2021 11:36:13 +0000 > x86_64 GNU/Linux > > $ gcc --version > gcc (GCC) 11.1.0 > > $ clang --version > clang version 13.0.0 (/home/uzu/.cache/yay/llvm-git/llvm-project > ad381e39a52604ba07e1e027e7bdec1c287d9089) > Target: x86_64-pc-linux-gnu > Thread model: posix > InstalledDir: /usr/bin > > P.S.: This issue was started in > https://github.com/libbpf/libbpf/issues/321 and brought to here. > > Thank you. > > Regards, > > Geyslan G. Bem
