shared-libraries

I need to build two 3rd party shared libraries, so their .so files will be reused by other projects. However, after build one of these libraries contains hardcoded path to another. This path is invalid on other machines and causes linker warnings. How can I prevent the full path from being embedded in the resulting .so files? Details: First library source: ~/dev/A Second library source: ~/dev/B Both of them have configure script to generate make files. Library B depends on A . So, first I build A : $ ~/dev/A/configure --prefix=~/dev/A-install $ make && make install Then I build B : $ ~/dev/B

I have a Python extension module that needs to link against some dynamic libraries at runtime, so I need to tell it where to look for them. I'm doing this by specifying runtime_library_dirs in my setup.py. This works fine on Linux, but seems to have no effect on Mac. I get an ImportError when I try to import my module, and the only way I've found to make it go away is to add the library directory to DYLD_LIBRARY_PATH before starting python. What do I need to do to make this work? I finally figured this out. The solution has two parts. First, setup.py needs to use extra_link_args to tell the

With respect to the following link: http://www.archlinux.org/news/libpnglibtiff-rebuilds-move-from-testing/ Could someone explain to me why a program should be rebuilt after one of its libraries has been updated? How does that make any sense since the "main" file is not changed at all? If the signatures of the functions involved haven't changed, then "rebuilding" the program means that the object files must be linked again. You shouldn't need to compile them again. An API is contract that describes the interface to the public functions in a library. When the compiler generates code, it needs

I need little clarification in this area. I feel that the terms Static library & Dynamic Library are not correct. lib1.o + lib2.o + lib3.o --> "LinkerOutputFile"(executable or library). If this "LinkerOutputFile" contains the code of all the files lib1.o , lib2.o, lib3.o then its said that "LinkerOutputFile" is satically-linked "LinkerOutputFile"(executable or library). (or) If "LinkerOutputFile" just contains references & other information about to lib1.o, lib2.o, lib3.o without containing the code of these lib*.o files. Then its said that "LinkerOutputFile" Dynamically linked. How does this

I'm looking for the tool / command on Unix platform to detect the library dependencies of the .so and .o files. I have already used the ldd / nm / truss , but I don't know the proper approach to detect library dependencies. It depends on what exactly is meant by "detect library dependencies". The ldd command works on shared libraries, not just on executables. It will display the dependencies of a shared library declared when the library was built: $ ldd /usr/lib/libgtk-3.so linux-vdso.so.1 (0x00007ffff8fff000) libgdk-3.so.0 => /usr/lib/libgdk-3.so.0 (0x00007f43fcf47000) libgmodule-2.0.so.0 =>

How can I force using a local library over the system library in linux? I linked my executable explicitly to some .so files in my project/lib directory e.g. (../lib/libluajit.so). Running my executable under gdb or using ldd shows that it still uses the system libluajit-5.1.so.2 I then set LD_LIBRARY_PATH to my project/lib directory and exported it, then ran my executable. Somehow it's still picking up the system library (confirmed by both gdb and ldd) I'd like to know how that's even possible, and what I can do to force it to use the local libluajit.so in my project/lib directory. When you

For instance: void* sdl_library = dlopen("libSDL.so", RTLD_LAZY); void* initializer = dlsym(sdl_library,"SDL_Init"); Assuming no errors, initializer will point to the function SD_Init in the shared library libSDK.so. However this requires knowing the symbol "SDL_Init" exists. Is it possibly to query a library for all its symbols? Eg, in this case it would return SDL_Init, the function pointer, and any other symbols exported by libSDL.so. jweyrich There is no libc function to do that. However, you can write one yourself (though the code is somewhat involved). On Linux, dlopen() in fact returns

Can anyone guide on how to debug a JNI code on Linux using GDB debugger(if possible please suggest other options). -My JNI project when running on Linux is leading to a JVM crash. -The CPP code has been compiled into .so files. -I run the project like this : *java xyz.jar -commandline_args_to_project*. I have the Gdb installed but am not getting how we can debug the project using it. Also do I necessarily need to compile the .cpp files with -g option t debug .so files? Start your java application Look up the pid using top, ps, ... Start gdb with this pid Attach your program code Debug as usual