This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VM: version `GLIBC_2.29' not found (required by libEGL.so)

Part Number: TDA4VM

Hi, we run Ubuntu 18.04 LTS (GNU/Linux 5.4.40-ACU-1.1.1.3 aarch64) on tda4, when use libEGL.so, we have log:

./gpu_test: /lib/aarch64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by libEGL.so)
./gpu_test: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by libwayland-client.so.0)
./gpu_test: /lib/aarch64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by libdrm.so.2)
./gpu_test: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by libwayland-server.so.0)

Ubuntu 18.04's gcc version is 8.4.0, does TI have any idea to resolve this? Thanks!

  • Hello,

    libEGL.so is built as a part of the graphics driver stack. How are you sourcing your libEGL.so for Ubuntu 18.04?

    Regards

    Hemant

  • We got a executable file "gpu_test" supplied by TI, when I run it,log here:

    ./gpu_test: /lib/aarch64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by libEGL.so)
    ./gpu_test: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by libwayland-client.so.0)
    ./gpu_test: /lib/aarch64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by libdrm.so.2)
    ./gpu_test: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by libwayland-server.so.0)

    Actually, libEGL.so is in TI's SDK.

    So we run "strings libm.so.6 | grep GLIBC_" to check ubuntu's libm.so.6, we have:


    run "strings libm.so.6 | grep GLIBC_" to check ubuntu's libc.so.6, we have:

    And Ubuntu 18.04's gcc version is 8.4.0, ldd --version returns 2.27.

    Now we need libEGL.so、libwayland-client.so、libwayland-server.so、libdrm.so match glibc 2.27, can TI give us appropriate so files? Thanks!

  • Hello,

    This requires a custom build and is not supported by the SDK. We recommend reaching out to your TI representative to discuss this if it is still a problem.

    Regards

    Hemant