Marcelo Juchem

IIRC we didn't reach a good enough API regarding overload resolution. Sounds reasonable, though. I'll take a stab at it again.

Forgive me for jumping in on the discussion. After looking at the proposed changes, it seems like the PR basically wants to do 2 things: - enable/disable use of libproxy...

@yonghong-song of course, I'll run some tests here. @davemarchevsky yes. Will do that.

@yonghong-song it looks like it's the C++ standard used. I ran a simple script to compile an empty `main` with different C++ standards on clang 14 and 15. It worked...

@yonghong-song I'm sorry for having failed to mention. `/usr/bin/c++` points to self-built Clang 14.0.6. I've also tried Debian provided Clang 15. Both reproduced the error. I haven't tried GCC. Both...

Compiler version: ``` $ c++ --version clang version 14.0.6 (https://github.com/llvm/llvm-project.git f28c006a5895fc0e329fe15fead81e37457cb1d1) ```

@yonghong-song it is entirely possible to do so. I'm no cmake expert, but in order to merge them all under the same library, it seems to me that instead of...

@yonghong-song I failed to clarify this: if there's is a final decision that `api-static` and `clang-frontend` should be merged into `bcc-static`, I can go ahead and make the changes to...

@yonghong-song the latest patch merges `api-static` and `clang_frontend` into `libbcc`. While working on this I realized the same problem happened to `usdt-static` and `bcc-loader-static`, so they got merged as well....

@yonghong-song I apologize for having deleted my fork by mistake. I got it restored. The latest version should reflect everything you asked for.