Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot start on Ubuntu 20.04 #11

Open
ahobsonsayers opened this issue Apr 13, 2023 · 9 comments
Open

Cannot start on Ubuntu 20.04 #11

ahobsonsayers opened this issue Apr 13, 2023 · 9 comments

Comments

@ahobsonsayers
Copy link

ahobsonsayers commented Apr 13, 2023

When attempting to launch on my PC i get the following error

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

I have glibc already installed, but it seems to be the wrong version (maybe because it was compiled on another version of Ubuntu or different distribution all together)

Im wondering if it might be better to statically compile the binary?

@FrenchGithubUser
Copy link
Owner

This might be related to wails, and not to Hatt itself. I'll have a closer look

@FrenchGithubUser
Copy link
Owner

Could you try installing glibc6 as mentionned here ?

@ahobsonsayers
Copy link
Author

ahobsonsayers commented Apr 13, 2023

Already have it installed sadly

$ sudo apt install libc6
Reading package lists... Done
Building dependency tree       
Reading state information... Done
libc6 is already the newest version (2.31-0ubuntu9.9).
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.

Note glibc6 is installed via the libc6 pacakge

@ahobsonsayers
Copy link
Author

ahobsonsayers commented Apr 13, 2023

It does indeed look like a Wails issue however. As such im not sure this is up to Hatt to solve, unless statically compiling it is a possibility. Feel free to close if not.

Also worth noting these related golang issues:
golang/go#58550
golang/go#57328

@FrenchGithubUser
Copy link
Owner

Thanks for the references. I'll have a look at static compilation

@ahobsonsayers
Copy link
Author

ahobsonsayers commented Apr 13, 2023

Possibly another helpful link, I see that sqlc has managed to solve this issue. FYI sqlc works on my machine.

sqlc-dev/sqlc#2124

@FrenchGithubUser
Copy link
Owner

sqlc used static builds to fix the issue, right ? I could create static builds but it feels like a "dirty" solution...

@ahobsonsayers
Copy link
Author

sqlc did do that as far as i can see! I can't attest to whether it is "dirty" or not, but i do often find static binaries not being prone to issues like is a huge benefit.

Maybe a better, less "dirty" solution to this problem is to think about using an alternative method of distributing the app, such as a flatpak (my personal favourite), AppImage or snap pacakge.

I have been interested learning to build flatpak images, so might be able to find some time to look into this myself if you don't have time. I cant promise when this will be though!

@FrenchGithubUser
Copy link
Owner

Yea, AppImage or faltpak seem more interesting (as it is clearer that the binary comes with external libs that could be already installed). Please don't hesitate to let me know if you look into this !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants