3 ms·
In my experience, a lot of Linux programs aren't straightforward to compile statically. Having said that, that might just be my ineptitude! Which bit of the ca
by mwilliamson 13y ago
In my experience, a lot of Linux programs aren't straightforward to compile statically. Having said that, that might just be my ineptitude!
Which bit of the caching isn't clear? If you're happy that whack creates relocatable versions, then the caching works just by copying the output directory into ~/.cache, and then copying that directory to the target on subsequent installations. The exact details of how programs are made relocatable are under "How does Whack work?" in the README.
- X4 13y agoThank you, that answers my question No you're right, not all binaries can be statically linked easily, it's very tedious in these cases. Oh, no I hoped that something performance related is happening when you said cache, like tuning the binary, predictive read-ahead streaming of the binary to memory, or something like that. I didn't know that it's a copy operation.
- justincormack 13y agoSome programs rely on dynamic libraries for modules so you can't, but the main issue is glibc is not designed to support static linking. Use eg Musl as your libc and it is fine.