3 ms·
Don't be that misleading. That's the rust compiler. You should analyze an executable created by the rust compiler instead. AFAIK only glibc and libgcc are lin
by Shorel 4y ago
Don't be that misleading. That's the rust compiler.
You should analyze an executable created by the rust compiler instead.
AFAIK only glibc and libgcc are linked dynamically in a program written in rust, and there's a way to statically link these.
- steveklabnik 4y agoThe Rust compiler is an executable created by the Rust compiler.
- Shorel 4y agoAnd one of the very few, if not the only one, that have to link with LLVM.
- steveklabnik 4y agoThat's true, but many of them that use C libraries dynamically link to those libraries, even if it's not LLVM. OpenSSL is classic example.
- Shorel 4y agoThis entire conversation has managed to diminish my enthusiasm for Rust. =/
- imtringued 4y agoYou can write C libraries in Rust. The entire operating system could be written in Rust and there would still be be dynamic linking between programs. What you are complaining about is ABI stability between versions of Rust but you are hiding that by arguing steveklabnik is violating the spirit of your secret ideals.
- mwcampbell 4y agoIIUC though, the Rust compiler executables are highly unusual in that they dynamically link their main top-level dependency. The vast majority of executables built with cargo do not, and I'm not sure how easy it is for a cargo project to do what the compiler does, i.e. build a top-level crate as a DLL and dynamically link that, while using plenty of static linking within that DLL.