Comment by sesm
10 months ago
glibc is only 2 MB, why Chrome relies on system glibc instead of statically linking their own version with frame pointers enabled?
10 months ago
glibc is only 2 MB, why Chrome relies on system glibc instead of statically linking their own version with frame pointers enabled?
https://stackoverflow.com/questions/57476533/why-is-statical...
I guess the similar situation with msvcrt’s.
At the very least Chrome needs to link to the system libGL.so and friends for gpu acceleration, libva.so for video acceleration, and so on. And these are linked against glibc of course.
having/omitting frame pointers doesn't change the ABI; it will work if you compile against glibc-nofp and link against glibc-withfp