3 ms·
glibc is only 2 MB, why Chrome relies on system glibc instead of statically linking their own version with frame pointers enabled?
by sesm 3y ago
glibc is only 2 MB, why Chrome relies on system glibc instead of statically linking their own version with frame pointers enabled?
- wruza 3y agohttps://stackoverflow.com/questions/57476533/why-is-statically-linking-glibc-discouraged https://stackoverflow.com/questions/57476533/why-is-statical... I guess the similar situation with msvcrt’s.
- nolist_policy 3y agoAt 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.
- dooglius 3y agohaving/omitting frame pointers doesn't change the ABI; it will work if you compile against glibc-nofp and link against glibc-withfp