4 ms·
I'm assuming that you're also building all your dependent libraries as part of your build process, as is common with languages like Rust. Closed source librarie
by howinteresting 5y ago
I'm assuming that you're also building all your dependent libraries as part of your build process, as is common with languages like Rust. Closed source libraries are somewhat out of scope when talking about Linux distributions, though you can always ask the vendor to provide you a 64-bit compatible library.
- WJW 5y ago> though you can always ask the vendor to provide you a 64-bit compatible library This is not always true, as the vendor may have disappeared and can no longer provide new versions of the library for any reason. Though, if you knowingly have such a black box in your code and willingly keep running with it until 2038 then you kinda deserve what is coming.
- mlyle 5y agoThen it's not a distinction between dynamic linking and static linking. It's a distinction of "only link against things you yourself build and ship". It's nothing to do with closed or open source. I don't want to build a very big world, and ship a huge amount of binary code that can be found in distributions, to make a 2038-safe app.
- howinteresting 5y agoIt's not that big a world. And ststic linking in particular opens up a ton of other opportunities, such as monomorphization.