All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: "Geyslan G. Bem" <geyslan@gmail.com>
Cc: bpf <bpf@vger.kernel.org>
Subject: Re: kernel bpf test_progs - vm wrong libc version
Date: Mon, 14 Jun 2021 23:27:01 -0700	[thread overview]
Message-ID: <CAEf4BzZkK9X2RadSYUWV5oh960iwaw3y5EKr7zu8WZ7XnRYz6g@mail.gmail.com> (raw)
In-Reply-To: <CAGG-pUTpppu-voYuT81LiTMAUA5oAWwnAwYQVAhyPwj3CwnZPA@mail.gmail.com>

On Fri, Jun 11, 2021 at 1:23 PM Geyslan G. Bem <geyslan@gmail.com> 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

  reply	other threads:[~2021-06-15  6:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11 20:18 kernel bpf test_progs - vm wrong libc version Geyslan G. Bem
2021-06-15  6:27 ` Andrii Nakryiko [this message]
2021-06-15  8:06   ` Jussi Maki
2021-06-15  9:57     ` KP Singh
2021-06-15 12:32       ` Geyslan G. Bem
     [not found]         ` <CACYkzJ5odOMQzcbfnvJmW52uxs50FY1=kSbADvD4UCF9fh3X5w@mail.gmail.com>
     [not found]           ` <CAGG-pURQ4hxQe8w3zdW4y1hBRn1sGikB_5oodid_NHaw_U=9iw@mail.gmail.com>
2021-06-15 15:58             ` KP Singh
2021-06-15 16:40               ` Geyslan G. Bem
2021-06-15 19:00                 ` Andrii Nakryiko
2021-06-18 14:34                   ` KP Singh
2021-06-15 11:54   ` Geyslan G. Bem

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAEf4BzZkK9X2RadSYUWV5oh960iwaw3y5EKr7zu8WZ7XnRYz6g@mail.gmail.com \
    --to=andrii.nakryiko@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=geyslan@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.