New answers tagged shared-library
Static libraries are binary independent packages of compiled source code that you "import" in your application when build it in a static manner. Really, a program called linker, carry out a sort of "copy and paste" of their compiled code along with your compiled source code (it is a bit more complex but this explanation can be go well for respond to your ...
Static libraries are libraries used by binaries at compilation time. They are usually not used again in the runtime as they are linked with the compiled binary at the compilation time and become part of the binary itself. Also, in implementation, these are not shared among binaries, only the binary that is compiled with specific static library(ies), uses ...
This is not a security risk at all, because you can always only set environment variables for your current environment (e.g. current Bash session) and, using the export command, its child environments (scripts you launch, subshells, etc.). It's impossible to escalate an environment variable created or modified into the parent environment. This includes that ...
The static libraries are likely there because you have installed one or more of the C development packages - to see exactly which, you can query the package database e.g. $ dpkg -S libm.a libc6-dev-i386: /usr/lib32/libm.a libc6-dev:amd64: /usr/lib/x86_64-linux-gnu/libm.a libc6-dev-armel-cross: /usr/arm-linux-gnueabi/lib/libm.a
Top 50 recent answers are included