You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The initial issue appears to be compatibility with -flto, which redis uses at it's default optimization level. At link time, the compilation logs include the error:
/usr/bin/ld: /opt/mate/llvm-wedlock/bin/../lib/LLVMgold.so: error loading plugin: /opt/mate/llvm-wedlock/bin/../lib/LLVMgold.so: cannot open shared object file: No such file or directory
Commenting out the relevant lines of the Makefile improves things:
But the compilation still fails. It looks like this is because redis' build process uses separate invocations for compiling and linking each final executable:
Specifically, I believe GLLVM doesn't wrap ld at all, so it isn't aware of any embedded bitcode that gets shuffled around there. Maybe there's something we could do with Blight to fix this, like an action that replaces $(LD) with clang in linker mode.
A user reached out about an error ingesting
redis
(https://github.com/redis/redis) usingmate-cli oneshot redis
.The initial issue appears to be compatibility with
-flto
, whichredis
uses at it's default optimization level. At link time, the compilation logs include the error:Commenting out the relevant lines of the Makefile improves things:
But the compilation still fails. It looks like this is because redis' build process uses separate invocations for compiling and linking each final executable:
After a quick inspection, I wasn't able to track down what emits the final
DEBUG
message (clang itself?).The text was updated successfully, but these errors were encountered: