-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[clang] Cannot link against 32-bit version of libclang #7442
Comments
@mati865 any idea? |
I don't know the cause or the workaround. |
Unfortunately we are using LLVM 11 (11.0.0) and Rust 1.48.0: |
I have no idea how to debug such issues on Windows. The only thing about debugging I could find on Windows: https://stackoverflow.com/a/31588940/5940067 |
@mati865 On the topic of a minimal reproducible example: @Ilia-Kosenkov has written a minimal Rust program that just links libclang and does a single function call: https://github.com/Ilia-Kosenkov/rust_clang_run/blob/master/src/main.rs @Ilia-Kosenkov Given this minimal example, it may also be worth it to file an issue over at the clang-sys crate: https://github.com/KyleMayes/clang-sys |
Before filing more issues I want to make sure that it is indeed |
To provide a quick update: We now have discovered that the failure occurs only when we run the executable via |
This issue has previously been reported here: msys2/MSYS2-packages#2259 but the site for the mingw-w64-i686-clang package suggests filing here, so I'm doing this also. In brief, we cannot link against the 32-bit version of libclang. We get an error "The specified procedure could not be found. (os error 127)".
The problem is reproducible by multiple people, on multiple machines, and it only occurs with the 32-bit version. @Ilia-Kosenkov has been able to track it down to a problem with zlib1, which is loaded as part of loading libclang. See the detailed error log provided here: msys2/MSYS2-packages#2259
Pinging @elieux as he's listed as the signer of the package.
The text was updated successfully, but these errors were encountered: