If libncurses is not installed then install it and try again. for 32-bit binaries : sudo apt-get install libncurses5:i386 for 64-bit binaries : sudo apt-get install libncurses5 Also install the collection of libraries by using this command, sudo apt-get install ia32-libs
Android devices have CPUs. Many of those CPUs are based on the ARM architecture, while some are based on x86, and a few others are based on other stuff like MIPS. Some Android apps use the Native Development Kit (NDK) to create C/C++ code to link into their app. C/C++ code needs to be compiled … Read more
There are two ways to achieve that: Use -rpath linker option: gcc XXX.c -o xxx.out -L$HOME/.usr/lib -lXX -Wl,-rpath=/home/user/.usr/lib Use LD_LIBRARY_PATH environment variable – put this line in your ~/.bashrc file: export LD_LIBRARY_PATH=/home/user/.usr/lib This will work even for a pre-generated binaries, so you can for example download some packages from the debian.org, unpack the binaries and … Read more
Let’s say that logcat show you the following crash log (this is from one of my projects): I/DEBUG ( 31): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** I/DEBUG ( 31): Build fingerprint: ‘generic/sdk/generic:2.3/GRH55/79397:eng/test-keys’ I/DEBUG ( 31): pid: 378, tid: 386 >>> com.example.gltest <<< I/DEBUG ( 31): … Read more
Here is a simple example project to illustrate the use of -rdynamic. bar.c extern void foo(void); void bar(void) { foo(); } main.c #include <dlfcn.h> #include <stdio.h> #include <stdlib.h> void foo(void) { puts(“Hello world”); } int main(void) { void * dlh = dlopen(“./libbar.so”, RTLD_NOW); if (!dlh) { fprintf(stderr, “%s\n”, dlerror()); exit(EXIT_FAILURE); } void (*bar)(void) = dlsym(dlh,”bar”); … Read more
Assuming you are generating a shared library, most probably what happens is that the variant of liblog4cplus.a you are using wasn’t compiled with -fPIC. In linux, you can confirm this by extracting the object files from the static library and checking their relocations: ar -x liblog4cplus.a readelf –relocs fileappender.o | egrep ‘(GOT|PLT|JU?MP_SLOT)’ If the output … Read more
To find which library is being used you could run $ /sbin/ldconfig -p | grep stdc++ libstdc++.so.6 (libc6) => /usr/lib/libstdc++.so.6 The list of compatible versions for libstdc++ version 3.4.0 and above is provided by $ strings /usr/lib/libstdc++.so.6 | grep LIBCXX GLIBCXX_3.4 GLIBCXX_3.4.1 GLIBCXX_3.4.2 … For earlier versions the symbol GLIBCPP is defined. The date stamp … Read more
Difference Between .o, .a, .lo and .so. Executive Summary .o is typically a non-PIC object file emitted by the compiler (before linker stage) When linked with an exe, the code will be included in the executable — we bind at link time. .a is typically an archive library containing one or more .o files [non-PIC]. … Read more
.a files are static libraries typically generated by the archive tool. You usually include the header files associated with that static library and then link to the library when you are compiling.
Check out the linker option -z defs / –no-undefined. When creating a shared object, it will cause the link to fail if there are unresolved symbols. If you are using gcc to invoke the linker, you’ll use the compiler -Wl option to pass the option to the linker: gcc -shared … -Wl,-z,defs As an example, … Read more