-
-
Notifications
You must be signed in to change notification settings - Fork 324
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not compile libafl_cc
#1234
Comments
do you have |
Yup, I have |
ok, then Can you check if this is the right file, that has all the CLANG, LLVM_CC_LLVM_VERSION, definitions? |
Sure I can, except I don't know how. If it includes the aforementioned file, then it includes an empty file. |
Ok, after a bit of digging, I have verified that yes it is indeed the correct file. However, in in here Line 218 in 8ff8ae4
clang_constants.rs file, but only if it can't find llvm-config??
so the file is populated only if it doesn't find llvm-config? I'm confused. If I negate the if clause, I get the warning that llvm-config wasn't found but the file is populated. Namely with:
|
if llvm-config is installed. then it'll get populated here Line 271 in 8ff8ae4
|
ok I found the issue, why it can't find clang. It's because of this
If one installs the LLVM-tools on windows, it doesn't come with llvm-config, for that you have to compile the llvm-project yourself. Long story short, llvm-config and the clang executable are in two different locations. You can close this now :D |
Yes, if you can submit a pr that'll be helpful. We don't have anybody with access to windows now. |
Hi,
I'm trying to build the library using
cargo build --release
. However, the process terminates with the error:Now, I have installed LLVM-14.06 and I have also compiled the llvm-project (same version) to get the llvm-config executable. I have also set the path variable LLVM_CONFIG. The strange thing is that I have set the path to clang and I can compile with clang without problem.. here is the version:
Any suggestions appreciated.
The text was updated successfully, but these errors were encountered: