tauri: /usr/lib/libc.so.6: version `GLIBC_2.33' not found
Describe the bug I build my application on one machine, then I have a friend who tries to launch the appimage on another machine using another glibc version. They get the following error:
./my-app: /usr/lib/libc.so.6: version `GLIBC_2.33' not found (required by ./my-app)
To Reproduce Steps to reproduce the behavior:
- Build an appimage with one machine.
- Try to launch the appimage on another machine. (With another version of glibc.)
- See the error; the app does not launch.
Expected behavior I expect the appimage to “just work”, since as far as I know appimages should have static libraries and therefore launch on any machine.
Are there any solutions to this?
Platform and Versions (please complete the following information):
Operating System - Linux(5.11.4-zen1-1-zen) - linux/x64
Node.js environment
Node.js - 15.11.0
tauri.js - 0.14.1
Rust environment
rustc - 1.50.0
cargo - 1.50.0
tauri-bundler - 0.9.4
Global packages
NPM - 7.6.1
yarn - 1.22.10
App directory structure
/.git
/dist
/src-tauri
App
tauri.rs - 0.11.1
mode - embedded-server
build-type - bundle
CSP - default-src blob: data: filesystem: ws: http: https: 'unsafe-eval' 'unsafe-inline'
distDir - ../dist
devPath - http://localhost:4000
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 5
- Comments: 33 (16 by maintainers)
It should not be closed, I got the same issue and found no solution here! It’s not cross-platform at all!
Has anybody figured this out for tauri-v2-beta yet? I’m trying to get an appImage that will work on Centos Stream 9, but haven’t found an OS that will build for me yet.
It appears we need an OS with GLIBC <= 2.34 (to support CentOS Stream 9) and a gnome glib >= 2.70 (which is what it appears that Tauri needs).
Am I just going to have to build gnome from source?
Not sure if this would be helpful, but I’ve encountered the same issue, and I used zig cc to link against an older glibc version. Though my repo is for cross compiling to arm64, you can just ignore the cc stuff(if compiling for the same arch), and change the config(.cargo/config.toml) accordingly. REPO
In short: you can(?) compile for older systems with a newer glibc on the host machine.
Just built on arch based system and tried to run the Appimage on debian. failed missing GLIBC .
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38'I get that, but at some point we just have to cut our losses and admit that if a user is not keeping fundamental libs up to date then there isn’t much we can do about it - other than perhaps informing them to join the 21st century. 😛
sorry, I meant glibc not gcc https://redbeardlab.com/2019/05/07/rust-and-glibc-version/