libfoo

I have two (very long) c code files, foo1.c and foo2.c, and a library which I don't have access to its source code libfoo.a. In all three files, they use a function called MyFooFunc. Now I just want to intercept MyFooFunc calls from foo1.c, have my own implementation, but do not intercept the function calls in the other two files. Is there any way I can do that, without rename the MyFooFunc function name?

Thanks for any suggestions.

I want to use ASAN for a process on a system. The system requires another library libfoo to be loaded first. libfoo does not intercept any allocations.

From this trial, it looks like Docker's COPY command doesn't preserve symlinks -- rather, it "follows" symlinks and copies the target file(?):

Clang isn't able to find omp.h whenever I try to compile with openMP flag. Here's what I'm trying to do

I am currently building an autotools-based package for buildroot but I only need some parts of the actual build output (shared libraries and a handful of tools). Is there a way to install only what I need, similar to debian's *.install files when a package should be split up (like a libfoo and libfoo-dev package). If there is no other way, I will have to use the LIBFOO_POST_INSTALL_TARGET_HOOKS but I would like to know if there is a better option.

I know of the LIBFOO_CONFIG_SCRIPTS variable, but this only remove files in the /bin directory and I would like to remove them from other places too (libexec, /var, ...). This method also feels hacky for non-config scripts related to that library.

I am able to integarte a 64 bit prebuilt library "x" in android for arm platform and when i try calling that libary in required module which will compile for both 32bit and 64bit library failed mentioning 32 bit library of "x" is not found. /out/target/product/xxxx/system/lib64/libxxxx.so

1. prebuilt library makefile

I'm studying how the C++ linker (gnu linker here) resolves dependencies
between static libraries and shared libraries and stuck in a question as below for a while

There are 3 files as below

• main.cpp (which depends on foo.cpp)
• foo.cpp (which depends on boo.cpp)
• boo.cpp

I have makefile shared by multiple projects, which links shared libraries. The sources -- and the library-names -- are set by each project's own GNUmakefile.

When the library-name (${SO}) contains the version (such as libfoo.so.2) I need to create a symlink:

I have a libfoo.so library which I used it for architecture armeabi for my old Android system. Today I am building to new architecture arm64-v8a, I have configured correctly in gradle abiFilters += 'arm64-v8a', and I unzip my apk, I can find my libfoo.so library in myApp.apk/lib/arm64-v8a. I don't have source code for this libfoo.so library, so I used back previous one which is built for armeabi. But I got the error as below:

2020-11-17 20:56:23.039 13083-13556/? W/System.err: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/sg.com.aa.bb-1/base.apk"],nativeLibraryDirectories=[/data/app/sg.com.aa.bb-1/lib/arm64, /data/app/sg.com.aa.bb-1/base.apk!/lib/arm64-v8a, /system/lib64, /vendor/lib64]]] couldn't find "libfoo.so"

As you can see this path /data/app/sg.com.aa.bb-1/base.apk!/lib/arm64-v8a, I am pretty sure my libfoo.so file is inside, but why it keep saying couldn't find libfoo.so?

I run file command on the file libfoo.so, it shows:

ELF 32-bit LSB pie executable ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /system/, stripped

There are people asked similar question before, arm64-v8a should be compatible with those 32 bit library, like this. And this, it says 64-bit devices also support their 32-bit variants. Using arm64-v8a devices as an example, the device can also run armeabi and armeabi-v7a code. Note, however, that your application will perform much better on 64-bit devices if it targets arm64-v8a rather than relying on the device running the armeabi-v7a version of your application.

In this case, could it be other possibilities that cause the UnsatisfiedLinkError above?

Conclusion:

I finally got what @Jake mean, I am kind of confused with what so-called "arm64-v8a support 32 bit too". Yes, it does support but provided it runs in 64 bit mode, and once an Android app start in 64 bit mode, it can't execute any 32 bit C library. So I have to find a way to force the app to run in 32 bit mode.