Skip to content
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

Can't find clang on Ubuntu #28

Closed
jethrogb opened this issue Jun 5, 2016 · 4 comments
Closed

Can't find clang on Ubuntu #28

jethrogb opened this issue Jun 5, 2016 · 4 comments

Comments

@jethrogb
Copy link

jethrogb commented Jun 5, 2016

On Ubuntu, LLVM binaries have the version number appended to their name, like so:

$clang[TAB][TAB]
clang-3.5                     clang-format-diff-3.5
clang++-3.5                   clang-modernize-3.5
clang-apply-replacements-3.5  clang-query-3.5
clang-check-3.5               clang-tblgen-3.5
clang-format-3.5              clang-tidy-3.5

support::Clang::find can't find clang this way.

@KyleMayes
Copy link
Owner

Should be fixed by 1ef7a4f.

@jethrogb
Copy link
Author

Thanks!

@tatref
Copy link

tatref commented Jun 20, 2016

Same issue here on Debian 8.5.

The clang lib is /usr/lib/llvm-3.5/lib/libclang.so.1, but I had to create a link named libclang.so to get it to compile.

Error message follow:

Build failed, waiting for other jobs to finish...
error: failed to compile `bindgen v0.18.0`, intermediate artifacts can be found at `/tmp/cargo-install.7B4EzkrL0K9o`

Caused by:
  failed to run custom build command for `clang-sys v0.7.2`
process didn't exit successfully: `/tmp/cargo-install.7B4EzkrL0K9o/release/build/clang-sys-66118395f506ca26/build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at 'could not find libclang.so, set the LIBCLANG_PATH environment variable to a path where libclang.so can be found', /home/tatref/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.7.2/build.rs:42
note: Run with `RUST_BACKTRACE=1` for a backtrace.

It seems that the version I'm using should be clear of this bug?

@KyleMayes
Copy link
Owner

KyleMayes commented Jun 20, 2016

This issue was for finding the clang executable when it had a version number appended to it (e.g., clang-3.5), not the .so. Could you open a separate issue with what behavior you expect so I don't forget to fix this?

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants