Skip to content
Advertisement

Tag: static-linking

Why libtool runs ranlib for a static library installation?

I’m trying to understand why libtool runs ranlib when installing a static library. This is an example from the link: https://www.gnu.org/software/libtool/manual/html_node/Installing-libraries.html But, isn’t the index table already created and shouldn’t it be just a simple copy operation? I found running ranlib at the end of the copy redundant as the library already has an index. Thanks. Answer Back in the

C assembler function casting

I came across this piece of code (for the whole program see this page, see the program named “srop.c”). My question is regarding how func is used in the main method. I have only kept the code which I thought could be related. It is the line *ret = (int)func +4; that confuses me. There are three questions I have

gdb step not working as expected

I am debugging static multi-threaded x86-64 C++ application on Linux. I can set breakpoints on functions and stop on them and I can walk step by step over function body. But when I try to step into another function, gdb not stops at it’s beginning and it seems that it just continues execution. When I interrupt program execution, gdb goes

Linux static linking is dead?

In fact, -static gcc flag on Linux doesn’t work now. Let me cite from the GNU libc FAQ: 2.22. Even statically linked programs need some shared libraries which is not acceptable for me. What can I do? {AJ} NSS (for details just type `info libc “Name Service Switch”‘) won’t work properly without shared libraries. NSS allows using different services (e.g.

Advertisement