Closed crcastle closed 4 months ago
Thanks for calling this out.
I'll work on including a statically linked version of the build in the releases. IMO that'll be the best experience for people.
Thanks for calling this out.
I'll work on including a statically linked version of the build in the releases. IMO that'll be the best experience for people.
Great. Thanks! And thanks for creating this handly CLI!
Try one of the builds ending in "musl" and let me know how it goes: https://github.com/davidchalifoux/kaput-cli/releases/tag/v2.2.2
Worked on my Debian Bullseye (x86 64) with glibc 2.31.
On Tue, Apr 30, 2024, at 8:49 PM, David Chalifoux wrote:
Try one of the builds ending in "musl" and let me know how it goes: https://github.com/davidchalifoux/kaput-cli/releases/tag/v2.2.2
— Reply to this email directly, view it on GitHub https://github.com/davidchalifoux/kaput-cli/issues/53#issuecomment-2087935385, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACDKFXRUC3HUT4AKWXAE23ZABQ6LAVCNFSM6AAAAABG3PPGVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBXHEZTKMZYGU. You are receiving this because you authored the thread.Message ID: @.***>
Thanks for confirming! Let me know if you run into any other issues.
My machine has glibc v2.31 (Debian Bullseye), which was too old for the kaput version v2.2.1 release file kaput-x86_64-unknown-linux-gnu.tar.gz. I got the following error when trying to run that v2.2.1 binary:
Considering I'm not a Rust dev so don't have nor want to install
cargo
andrustc
, the easiest way for me to get a working binary was to create a statically linked binary using the following steps.Happy to make a PR to the README with these installation instructions if you'd like.
The current
rust
docker image contains glibc v2.36, but compiling kaput statically gets around that version not matching the v2.31 glibc on my Debian Bullseye host OS.