3 ms·
OK? As I said, it produces static executables that dynamically link with libc. I would not call that a dynamic executable, especially when already specifying th
by staticassertion 5y ago
OK? As I said, it produces static executables that dynamically link with libc. I would not call that a dynamic executable, especially when already specifying that libc is loaded dynamically. I don't think most people would classify "loads libc dynamically" as a "dynamic executable".
- jart 5y agoGentlemen there's no need to argue because you're both right. Yes, Rust linkage is predominantly static. However in order to link libc dynamically on System V, it officially speaking needs to be a dynamic object rather than an executable, in most cases. I just checked on my system with a Rust binary to confirm. The Elf64_Ehdr::e_type is set to ET_DYN rather than ET_EXEC.
- IshKebab 5y agoI think they would. You can get a fully static binary if you link with musl. That's common with Rust.