How to work around a package needing a newer glibc version?
hwittenborn opened this issue · 5 comments
I've been trying to figure this out for a while, but is there any way I can work around programs in an AppImage needing a glibc version more recent than the one on the host system?
I've yet to find out any solution, but I'm thinking there's got to be one since Snaps and Flatpaks manage the backporting of glibc versions just fine. I just have no clue how I could do the same with Flatpak.
Is there any known ways to do what I'm wanting?
I've tried linking glibc into my program, but for some reason it always leads in a segmentation fault. I'm not really sure what might be causing it, I could send over any needed info if it'd help though.
Just did some Googling, and this post on Stackoverflow got me my answer. I just started my executable with the linked ld-linux library and it all worked fine.
I've been trying to get this all working for the past few months on and off so I can't guarantee I've reached my solution, but I'll reach out if there's any other issues I have.
Check https://github.com/probonopd/go-appimage/tree/master/src/appimagetool -s deploy to bundle everything including glibc ld-linux.
Just found out about the linuxdeployqt tool earlier, looks like that Go tool would be a bit nicer to use though. Thanks!
linuxdeployqt does not have the capability to bundle everything.