![Ditching a Microsoft Job to Enter Startup Hell with Lonewolf Engineer Sam Crombie [Podcast #171]](https://cdn.hashnode.com/res/hashnode/image/upload/v1746753508177/0cd57f66-fdb0-4972-b285-1443a7db39fc.png?#)
Is a "dynamically-linked executable" ever referred to as that?
Example When I run file on android-studio/bin/studio, I see: android-studio/bin/studio: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=b4be78977494d9024646ef0e45685a4152512800, for GNU/Linux 3.2.0, not stripped The section of that which matters for this is "ELF" and "dynamically linked". Question Considering that it appears that statically linking an ELF is possible, would I describe this as a "dynamically linked executable", as opposed to the common "dynamically linked library"? Rationale I ask because I have to use "s on Google to see any matches (which could be Google being "helpful" by default), but even then, the results are from very niche locations. Perhaps that's expected, though? I'm asking for confirmation from someone who's familiar with this.
Example
When I run file on android-studio/bin/studio, I see:
android-studio/bin/studio: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter/lib64/ld-linux-x86-64.so.2, BuildID[sha1]=b4be78977494d9024646ef0e45685a4152512800, for GNU/Linux 3.2.0, not stripped
The section of that which matters for this is "ELF" and "dynamically linked".
Question
Considering that it appears that statically linking an ELF is possible, would I describe this as a "dynamically linked executable", as opposed to the common "dynamically linked library"?
Rationale
I ask because I have to use "s on Google to see any matches (which could be Google being "helpful" by default), but even then, the results are from very niche locations. Perhaps that's expected, though? I'm asking for confirmation from someone who's familiar with this.
