dynamic-linking

I have a shared library that is linked with another (third-party) shared library. My shared library is then loaded using dlopen in my application. All this works fine (assuming files are in the proper path etc). Now, the problem is that I don't even need to specify to link against the third-party shared library when I link my library. GCC accept it without reporting errors about undefined references. So, the question; how can I force GCC to notify me about undefined references ? If I change my library to be (temporarily) an executable, I get undefined references (when not supplying the library

I read some articles discouraging of the use of DYLD_LIBRARY_PATH, as the the path of dynamic library should be fixed using -install_name, @rpath, and @loader_path. In terms of making a program that runs both on Linux and Mac OS X, DYLD_LIBRARY_PATH of Mac OS X does exactly what LD_LIBRARY_PATH of Linux. And, we can share (almost) the same make file that doesn't have the -install_name and @rpath. Is this OK to use DYLD_LIBRARY_PATH on Mac OS X? What's the dynamic library search algorithm with Mac OS X when the binary can't find the dynamic library? current directory -> DYLD_LIBRARY_PATH

I link with two different shared libraries. Both libraries define some symbols that share a name but have different implementations. I can't make each library use its own implementation over the other. For example, both libraries define a global function bar() that each calls internally. Library one calls it from foo1() and library two calls it from foo2() . Lib1.so: T bar T foo1() // calls bar() Lib2.so: T bar T foo2() // calls bar() If I link my application against Lib1.so and then Lib2.so the bar implementation from Lib1.so is called even when calling foo2() . If on the other hand, I link

I am trying to create a static object written in Go to interface with a C program (say, a kernel module or something). I have found documentation on calling C functions from Go, but I haven't found much on how to go the other way. What I've found is that it's possible, but complicated. Here is what I found: Blog post about callbacks between C and Go Cgo documentation Golang mailing list post Does anyone have experience with this? In short, I'm trying to create a PAM module written entirely in Go. You can call Go code from C. it is a confusing proposition though. The process is outlined in the

I'm trying to write a simple shared library that would log malloc calls to stderr (a sort of 'mtrace' if you will). However, this is not working. Here's what I do: /* mtrace.c */ #include <dlfcn.h> #include <stdio.h> static void* (*real_malloc)(size_t); void *malloc(size_t size) { void *p = NULL; fprintf(stderr, "malloc(%d) = ", size); p = real_malloc(size); fprintf(stderr, "%p\n", p); return p; } static void __mtrace_init(void) __attribute__((constructor)); static void __mtrace_init(void) { void *handle = NULL; handle = dlopen("libc.so.6", RTLD_LAZY); if (NULL == handle) { fprintf(stderr,