3 ms·
If you want portable apps just make one fully staticly compiled binary. This is the worst of all worlds. No security updates for used libraries and no performa
by sprash 7y ago
If you want portable apps just make one fully staticly compiled binary.
This is the worst of all worlds. No security updates for used libraries and no performance gain that comes with static linking.
- zurn 7y agoThe static linking ship has sailed years ago for glibc based apps (no static linking support).
- sprash 7y agoAlways use musl for static linking. As a bonus you might get an even smaller binary than a dynamically linked glibc binary.
- cesarb 7y agoKeep in mind, however, that AFAIK musl won't respect /etc/nsswitch.conf, so if for instance the machine is configured to lookup users on ldap, a musl static linked program won't be able to correctly lookup users.
- beatgammit 7y agoThere are certainly cases where you need the features of glibc over musl, but those are pretty rare IMO, and you can always implement a missing piece yourself if using musl saves you enough in maintenance overhead.