Well what I'm saying is this: If I have a binary, my_binary, and an SO, load_me.so. When my_binary is executed, it does nothing for, 10 seconds, then dynamically loads "load_me.so". Let's assume that load_me.so uses strlen() internally, and as such, ld would most likely link in libc...what I want is for libc and all the other crap to not be linked in, because these symbols will exist in my_binary.
Now, I may be getting ahead of myself, and -fPIC/-fpic may do this for me already.... I'll look into it
Why worry about this? It is the job of the dynamic linker. Most likely libc won't strictly be linked to the library, instead it'll just be linked to your process (because you ran my_binary) and not linked again to the library. That was my impression of dynamic linking; loading into the symbol space when needed. All functions in all linked libraries execute the same "instance" of strlen() within a single process. Jason -- If you understand, things are just as they are. If you do not understand, things are just as they are.