Re:Deno on MDN
by skywal_l on Monday August 23, 2021 @01:14PM
(#28279005)
[ Parent
| on HN ]
So, it's still linked against glibc and libgcc from what I can see almost all the following are from glibc):
$ ldd deno
linux-vdso.so.1 (0x00007fff3fbeb000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007efd30939000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007efd30721000)
librt.so.1 => /lib64/librt.so.1 (0x00007efd30519000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007efd302f9000)
libm.so.6 => /lib64/libm.so.6 (0x00007efd2ff77000)
libc.so.6 => /lib64/libc.so.6 (0x00007efd2fbb2000)
/lib64/ld-linux-x86-64.so.2 (0x00007efd34593000)
But honestly, that's pretty minimal. Just over 80 MB for the base to not have much in the way of dependencies seems pretty good. And given that library extensions are supposed to mostly be done in Rust (if that hasn't changed), those are statically linked by default as well, so that will hopefully cut down on accidentally introducing dependencies from the system it's built on also.