GLIBC_2.29
Hello i have problem my Wasp say : .local/share/wasp-lang/0.14.2/wasp-bin: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /home/*/.local/share/wasp-lang/0.14.2/wasp-bin) can you help me ? Thanks
10 Replies
Hi @MonsieurAki. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Sure, I can help with that. The error message you're seeing is because your system's version of the GNU C Library (glibc) is older than the version Wasp was compiled against. Wasp requires at least glibc 2.29 to run.
There are a few ways to resolve this issue:
1. Upgrade your system's glibc version: This is the most straightforward solution, but it can be risky because other applications on your system might depend on the older version of glibc. Be sure to check the compatibility of your applications before proceeding with this option.
2. Upgrade your system: If you're using an older version of your operating system, upgrading to a newer version might also upgrade glibc. For example, a user reported that upgrading to Ubuntu 21.10 (which uses glibc 2.34) resolved this issue for them (source (https://github.com/wasp-lang/wasp/issues/867)).
3. Wait for a statically linked version of Wasp: The Wasp team is aware of this issue and is considering building Wasp as a statically linked binary, which would not depend on the system's glibc version (source (https://github.com/wasp-lang/wasp/issues/650)). However, this has not been implemented yet.
In the meantime, you can check your current glibc version by running
ldd --version in your terminal. If the version is less than 2.29, you'll need to upgrade it or your system to use Wasp.
Please note that these solutions require a certain level of system administration knowledge. If you're not comfortable with these steps, you might want to ask for help from someone who is.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @MonsieurAki, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?i make : ldd --version and have : ldd (GNU libc) 2.28
i deploy in a web hosting service and i think i can't change ldd (GNU libc) to 2.29
or try : wget -c https://ftp.gnu.org/gnu/glibc/glibc-2.29.tar.gz
tar -zxvf glibc-2.29.tar.gz
mkdir glibc-2.29/build
cd glibc-2.29/build
../configure --prefix=/opt/glibc
make
make install
?
Where are you deploying your app?
in my website on https://www.o2switch.fr/ it's a french hosting service
i use the console in the user space
Are you using Docker to deploy or are you just running
wasp start on the machine directly?
Wasp compiler needs the GLIBC 2.29, but when you build the app, it's just a Node.js + React app which doesn't have those requirements. So usually, you develop locally with wasp start and when you deploy to a server, you are just deploying the built artefacts: https://wasp-lang.dev/docs/advanced/deployment/manually
Does that make sense to you? Are you able to do it like that?Deploying Manually | Wasp
This document explains how to build and prepare your Wasp app for deployment.
i just running wasp start on the machine directly
i need start in my computer localy before ? i use https://usemage.ai/
Wohooo @MonsieurAki, you just became a Waspeteer level 2!
Ok, so you are running the
wasp start development command directly on a Linux server. You should either try developing on your own machine and then deploy the built app to the server or try updating the GLIBC dependency on the server if possible.ok thanks i try it