I've got this error with buildroot-2022.11 when executing make.

Ubuntu 20.04 - added this repo as described in the link

sudo apt update
sudo apt install libc6

It automatically installed 2.35 for me.

Answer from mister_kanister on Stack Overflow
🌐
Ask Ubuntu
askubuntu.com › questions › 1526185 › how-to-install-glibc-2-34-on-ubuntu-20-04
How to install GLIBC_2.34 on Ubuntu 20.04 - Ask Ubuntu
September 9, 2024 - To run a program that is designed for internal use, it requires GLIBC_2.34. Ubuntu 20.04 is installed on the computer, where GLIBC_2.31 is available. How do I install GLIBC_2.34 on Ubuntu 20.04 or ...
Discussions

Glibc 2.34 and ubuntu 20.04
Describe the bug After the last update lens is not opening on ubuntu 20.04. I got the below error when running: A JavaScript error occurred in the main process Uncaught Exception: Error: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.... More on github.com
🌐 github.com
19
May 9, 2025
Problem when running on Ubuntu 20.04
I've had a similar problem. My solution was to build the app in a Ubuntu docker container and then copy the resulting binary from that container. The Dockerfile I've used looked like this: # Dockerfile for building a rust executable that can be run on a specific Ubuntu version (and newer) FROM ubuntu:20.04 RUN apt update && apt -y install curl build-essential RUN curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y RUN ~/.cargo/bin/rustup update WORKDIR /rust/build/ COPY Cargo.toml Cargo.toml COPY Cargo.lock Cargo.lock # Docker will cache a step as long as there haven't been any changes to the files. # This will download and build all the dependencies and will re-run only when Cargo.toml/Cargo.lock will change RUN mkdir -p src/bin && echo "fn main() {}" > src/bin/docker_cache.rs && /bin/bash -c "source ${HOME}/.cargo/env && cargo build --release --bin docker_cache && exit 0" COPY . . RUN ["/bin/bash", "-c", "source ${HOME}/.cargo/env && cargo build --release"] # USAGE: # docker build -t tmp/ubuntu20:build # if [ $? == 0 ]; then # docker container create --name extract tmp/ubuntu20:build # docker container cp extract:/rust/build/target/release/EXECUTABLE_NAME ./ # docker container rm extract # fi Edit: reddit did terrible things to formatting, this will hopefully be fixed now More on reddit.com
🌐 r/rust
8
3
August 10, 2023
GLIB : ERROR /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found
But when i tried to run the application in different ubuntu machine with (Ubuntu GLIBC 2.31-0ubuntu9.14) 2.31 I got the error saying ./source: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34’ not found (required by ./source) Does this mean, GLIB is not backward compatible? More on discourse.gnome.org
🌐 discourse.gnome.org
9
0
January 24, 2024
Glibc_2.34 ? - Kubuntu Forums
/installer: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./installer) What am I doing wrong? ... I'll Ask Jeeves...... ... What are you trying to install, exactly? Links? Ubuntu 22.04 has glibc 2.35 For some reason this thing wants an older version, which usually ... More on kubuntuforums.net
🌐 kubuntuforums.net
March 22, 2024
🌐
Ubuntu
launchpad.net › ubuntu › +source › glibc › 2.34-0ubuntu2
https://launchpad.net/ubuntu/+source/glibc/2.34-0u...
Ubuntu Developers · Architectures: any all · Section: libs · Urgency: Medium Urgency · Impish: amd64 arm64 armhf i386 ppc64el riscv64 s390x · diff from 2.33-0ubuntu9 to 2.34-0ubuntu2 (1.8 MiB) diff from 2.34-0ubuntu1 to 2.34-0ubuntu2 (5.3 KiB) View changes file · glibc-doc: No summary available for glibc-doc in ubuntu impish.
🌐
GitHub
github.com › lensapp › lens › issues › 8210
Glibc 2.34 and ubuntu 20.04 · Issue #8210 · lensapp/lens
May 9, 2025 - Describe the bug After the last update lens is not opening on ubuntu 20.04. I got the below error when running: A JavaScript error occurred in the main process Uncaught Exception: Error: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /opt/Lens/resources/app.asar.unpacked/node_modules/node-pty/build/Release/pty.node) at process.func [as dlopen] (node:electron/js2c/node_init:2:2569) at Module._extensions..node (node:internal/modules/cjs/loader:1741:18) at Object.func [as .node] (node:electron/js2c/node_init:2:2796) at Module.load (node:internal/modules/cjs/loader:12
Author   lensapp
Top answer
1 of 2
6

You can use following commands to bring in newer version of glibc in ubuntu 20.04, but note that as it is a system package, upgrading it may impact your system.

apt-get install gawk bison gcc make wget tar -y
wget -c https://ftp.gnu.org/gnu/glibc/glibc-2.35.tar.gz
tar -zxvf glibc-2.35.tar.gz && cd glibc-2.35
mkdir glibc-build && cd glibc-build
../configure --prefix=/opt/glibc
make
make install
2 of 2
0

Introducing glibc will break your core binaries. Updated core binaries require a newer kernel which breaks hardware drivers (like NVIDIA) that need your old kernel. This "vicious cycle" makes it impossible to use new glibc w/o breaking your system.

The only solution is to compile the unsupported drivers somehow for the new kernel. So far this is not possible.

If you try using GLIBC without updating its dependencies, you will get complaints of a version mismatch on its dependencies which go all the way down to the kernel, which is why it is not possible.

Your options are limited and it is not possible unless you use a virtual machine. But likely VM is not what you want because VMs do not have the advantage of talking to your hardware directly. They have some VM extensions for making that better but they only cover CPU and RAM, not the video/sound card, that is all emulated.

Summary

If you want to run something that needs newer hardware, there is just no way around that:

  1. You cant use unsupported hardware on newer kernel, and therefore linker, and then GLIBC.

  2. You can't use unsupported GLIBC on older kernel which relies on the new kernel features. If you try to do it by force (point to new compiled version of the new binaries) you will get an error that the linker/kernel versions are incorrect.

  3. The only solution to this is if there was a way to update your hardware drivers. If that isn't your problem, then UPGRADE UBUNTU to the latest version. If that IS your problem, then you are out of luck.

  4. Companies like NVIDIA and AMD drop video support after a few years and leave you up a creek with no paddle, stranded on an old OS unless you buy yet another video card (even if your current one is fast and does just fine, they do NOT care).

  5. Sandboxing in flatpak still needs those libraries to be able to link with your kernel. Sandboxing only fixes dependencies that are above the base system level. HOWEVER, if any of those libraries were built against a binaries that recursively rely on newer core libraries, you will still be stuck and it will still not work, below is an example:

/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found
(required by /tmp/.mount_my2newapp.a9fz3/usr/bin/../../usr/lib/liblzma.so.5)

As you can see here, even though the appimage/flatpak/snap was sandboxed, it still needed these new libraries further down the dependency chain.

🌐
Linux Mint Forums
forums.linuxmint.com › board index › main edition support › beginner questions
[SOLVED] `GLIBC_2.34' not found - Linux Mint Forums
November 8, 2022 - java: /lib/x86_64-linux-gnu/libc.so.6: ... `GLIBC_2.34' not found (required by /usr/lib/jvm/java-11-openjdk-amd64/bin/../lib/jli/libjli.so) Tried to download glibc-source, it didn't work. Not sure what else to try. inxi output: ... System: Kernel: 5.18.15-051815-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.2.7 wm: muffin 5.2.1 dm: LightDM 1.30.0 Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal ...
🌐
Reddit
reddit.com › r/rust › problem when running on ubuntu 20.04
r/rust on Reddit: Problem when running on Ubuntu 20.04
August 10, 2023 -

When i tryed to run my app with Ubuntu 20.04, i got a error :

asbackup: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by asbackup)
asbackup: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by asbackup)
asbackup: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by asbackup)

I trying to find a web some guide, but i don't know how to fix this

Top answer
1 of 2
2
I've had a similar problem. My solution was to build the app in a Ubuntu docker container and then copy the resulting binary from that container. The Dockerfile I've used looked like this: # Dockerfile for building a rust executable that can be run on a specific Ubuntu version (and newer) FROM ubuntu:20.04 RUN apt update && apt -y install curl build-essential RUN curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y RUN ~/.cargo/bin/rustup update WORKDIR /rust/build/ COPY Cargo.toml Cargo.toml COPY Cargo.lock Cargo.lock # Docker will cache a step as long as there haven't been any changes to the files. # This will download and build all the dependencies and will re-run only when Cargo.toml/Cargo.lock will change RUN mkdir -p src/bin && echo "fn main() {}" > src/bin/docker_cache.rs && /bin/bash -c "source ${HOME}/.cargo/env && cargo build --release --bin docker_cache && exit 0" COPY . . RUN ["/bin/bash", "-c", "source ${HOME}/.cargo/env && cargo build --release"] # USAGE: # docker build -t tmp/ubuntu20:build # if [ $? == 0 ]; then # docker container create --name extract tmp/ubuntu20:build # docker container cp extract:/rust/build/target/release/EXECUTABLE_NAME ./ # docker container rm extract # fi Edit: reddit did terrible things to formatting, this will hopefully be fixed now
2 of 2
1
Eugay is correct, but also want to add that instead of statically compiling with musl, you can also decide to maintain a "Ubuntu 20.04" version. To do so, just put your source code onto Ubuntu 20.04 and compile it there. The resulting binary will then be able to run on Ubuntu 20.04.
🌐
Ubuntu
launchpad.net › ubuntu › +source › glibc › 2.34-0ubuntu3
glibc 2.34-0ubuntu3 source package in Ubuntu - Launchpad
September 28, 2021 - Ubuntu Developers · Architectures: any all · Section: libs · Urgency: Medium Urgency · Impish: amd64 arm64 armhf i386 ppc64el riscv64 s390x · diff from 2.34-0ubuntu2 to 2.34-0ubuntu3 (22.2 KiB) View changes file · glibc-doc: GNU C Library: Documentation ·
Find elsewhere
🌐
GNOME Discourse
discourse.gnome.org › development
GLIB : ERROR /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found - Development - GNOME Discourse
January 24, 2024 - Hi, I’m working on GTK3 desktop application in cpp. I built my application on an ubuntu machine with (Ubuntu GLIBC 2.35-0ubuntu3.5) 2.35 and i was able to run this application on that machine. But when i tried to run the application in different ubuntu machine with (Ubuntu GLIBC 2.31-0ubuntu9.14) 2.31 I got the error saying ./source: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34’ not found (required by ./source) Does this mean, GLIB is not backward compatible?
🌐
Ubuntu
launchpad.net › ubuntu › +source › glibc › 2.34-0ubuntu2 › +build › 22036279
amd64 build : 2.34-0ubuntu2 : glibc package : Ubuntu
glibc - 2.34-0ubuntu2 · Archive: Primary Archive for Ubuntu · Series: Impish · Architecture: amd64 · Pocket: Proposed · Component: main · Binary packages produced by this build: glibc-doc 2.34-0ubuntu2 · glibc-source 2.34-0ubuntu2 · libc-bin 2.34-0ubuntu2 ·
🌐
Kubuntu Forums
kubuntuforums.net › forum › general › kubuntu-catchall › 677528-glibc_2-34
Glibc_2.34 ? - Kubuntu Forums
March 22, 2024 - /installer: /lib/x86_64-linux-... to install, exactly? Links? Ubuntu 22.04 has glibc 2.35 For some reason this thing wants an older version, which usually means it was built for older Linux versions....
🌐
GitHub
github.com › gitbutlerapp › gitbutler › issues › 4881
Does not run on Ubuntu 20.04 due to missing GLIBC 2.32+ libraries · Issue #4881 · gitbutlerapp/gitbutler
September 11, 2024 - While there is both a deb package and an appimage available for download, git-butler fails to run from both of these due to missing GLIBC 2.32/2.33/2.34 library requirements. I suspect it is due to this change, changing the target OS the deb/appimage is built against to Ubuntu 22.04.
Author   gitbutlerapp
🌐
Ubuntu Community Hub
discourse.ubuntu.com › project discussion › foundations
Migrating glibc 2.34 - Foundations - Ubuntu Community Hub
August 30, 2021 - Hi everyone, glibc is in impish-proposed now and the autopkgtests have all completed. As usual there are a bunch of failures, some glibc related and some not but all need attention before it can migrate to release. The…
🌐
Ubuntu
launchpad.net › ubuntu › jammy › +source › glibc
Jammy (22.04) : glibc package : Ubuntu
A newer version of glibc is available for packaging: GLibC 2.42 · Show upstream links · 2.34-0ubuntu3 · 2.35-0ubuntu1 · 2.35-0ubuntu1 · 2.35-0ubuntu2 · 2.35-0ubuntu3 · 2.35-0ubuntu3 · 2.35-0ubuntu3.1 · 2.35-0ubuntu3.1 · 2.35-0ubuntu3.2 · 2.35-0ubuntu3.3 ·
Top answer
1 of 2
3

It should be noted that https://abrok.eu/stockfish/ is not official, author clearly says that the packages were compiled with gcc 11.2/mingw 10 on Ubuntu 21.10.
While you are running 20.04 LTS which is older, so has older libc and other core system components.

I see two possible solutions:

  • Official packages from the developer

    The StockFish package for Ubuntu lists the following URL as developer's web-site https://stockfishchess.org . So you should visit https://stockfishchess.org/download/linux/ and then download relevant software distribution. For the time of writing it maybe done programmatically as follows:

    cd ~/Downloads
    wget -c https://stockfishchess.org/files/stockfish_14.1_linux_x64_avx2.zip
    unzip stockfish_14.1_linux_x64_avx2.zip
    cd stockfish_14.1_linux_x64_avx2
    chmod +x stockfish_14.1_linux_x64_avx2
    

    and then run it as ./stockfish_14.1_linux_x64_avx2.

    Note: it runs even on 18.04 LTS, does not complain about libc.

  • Some third-party PPA

    Finding PPA for StockFish is possible. It will end with for example StockFish 12.2 deb-package for 20.04 LTS, which may be installed by using below commands:

    sudo add-apt-repository ppa:savoury1/games
    sudo apt-get update
    sudo apt-get install stockfish
    

    Note: I'm not sure about AVX2 optimisation here.

    Reverting to default 11.1 version is possible by using below commands:

    sudo apt-get install ppa-purge
    sudo ppa-purge ppa:savoury1/games
    
2 of 2
0

I had the same issue with Stockfish 15 on Ubuntu 20.04. However it's not too difficult to compile from source following the directions at https://github.com/official-stockfish/Stockfish#compiling-stockfish-yourself-from-the-sources

cd src
make help

then check the latest arch supported, ex. grep bmi2 /proc/cpuinfo and make with the appropriate arch:

make net 
make build ARCH=x86-64-bmi2
🌐
GitHub
github.com › shellphish › how2heap › issues › 169
Not working on ubuntu 22.04, version `GLIBC_2.34' not found · Issue #169 · shellphish/how2heap
November 26, 2023 - Hello, compiling PoC on ubuntu 22.04 docker image will link to the /lib/x86_64-linux-gnu/libc.so.6 and not a specific libc version This problem only occurs when using ubuntu 22.04 ubuntu 20.04 works fine ... apt update apt -y install patchelf zstd python-is-python3 make git gcc git clone https://github.com/shellphish/how2heap cd how2heap make clean all ./glibc_run.sh 2.31 ./malloc_playground -r
Author   shellphish
🌐
Ubuntu Forums
ubuntuforums.org › showthread.php
Ubuntu Forums
A help and support forum for Ubuntu Linux.
🌐
BeagleBoard
forum.beagleboard.org › general discussion
libc.so.6: version `glibc_2.34' not found - General Discussion - BeagleBoard
January 10, 2024 - My computer’s OS is Ubuntu 22.04. I use eclipse c to develop beagleplay’s Linux app. When debugging, the error message libc.so.6: version `glibc_2.34’ not found (required by helloworld…) will appear. My computer glibc ve…
🌐
Stack Overflow
stackoverflow.com › questions › 76335067 › getting-glibc-2-34-not-found-error-while-running-go-geos-package-on-ubuntu-20
glibc - Getting `GLIBC_2.34` not found error while running go-geos package on Ubuntu 20.04 - Stack Overflow
You compiled the package linked against a different version of glibc than on the target platform. The easiest way to build this is on the target platform, provided you can install the correct dependencies.