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

Could not open library 'clang' #20

Closed
mattvague opened this issue Jul 25, 2013 · 16 comments
Closed

Could not open library 'clang' #20

mattvague opened this issue Jul 25, 2013 · 16 comments

Comments

@mattvague
Copy link

Not sure if this is an issue with ffi-gen or not but when I try and run ffi-gen I get the following error:

`block in ffi_lib': Could not open library 'clang': /usr/lib/clang: cannot read file data: Is a directory. (LoadError)
Could not open library 'libclang.so': libclang.so: cannot open shared object file: No such file or directory

Mind helping me out? I'm on Ubuntu and installed clang with apt-get but not sure what else i need to do to get it working.

Thanks!

@neelance
Copy link
Owner

I don't remember exactly in which package libclang.so is. You can use apt-file to find out: apt-file search libclang.so (you may need to install and update apt-file first). Also, in current Ubuntu repository is a newer version than 3.0. It might work, haven't tested. Good luck! :-)

@mvz
Copy link

mvz commented Aug 25, 2013

On Debian, at least, there is no /usr/lib/libclang.so, only /usr/lib/llvm-3.2/lib/libclang.so.

@kernelsmith
Copy link

was libclang-dev for me

@sheerun
Copy link
Contributor

sheerun commented Nov 16, 2014

We need Dockerfile for testing. There's no way all contributors need to setup dylibs first.

@mvz
Copy link

mvz commented Nov 17, 2014

@sheerun that's a consideration for OSX, right?

@sheerun
Copy link
Contributor

sheerun commented Nov 17, 2014

Not only OSX. It's not easy to get reproducible environment even on Linux.

@mvz
Copy link

mvz commented Nov 21, 2014

In the end, ffi_gen should run on the system itself, so while a Dockerfile may streamline development (I have no experience with that), things should also work without.

@sheerun
Copy link
Contributor

sheerun commented Nov 21, 2014

Yes, of course. Dockerfile is only for development.

@whitequark
Copy link
Collaborator

On Debian and derivatives (with recent LLVM at least), due to multilib, the file is located in /usr/lib/x86_64-linux-gnu/libclang.so.1, not only in /usr/lib/llvm-x.y/lib/libclang.so.1. Anyway, this is fixed in master.

@sheerun
Copy link
Contributor

sheerun commented Jan 25, 2015

@whitequark We still need dockerfile. Can you repopen this issue or create new issue?

@whitequark
Copy link
Collaborator

@sheerun I don't understand the value provided by this... contributors are a small subset of users, and users will have to figure out the OS packaging anyway.

@sheerun
Copy link
Contributor

sheerun commented Jan 25, 2015

So it's easier for contributors to write test cases and pull-requests regardless of OS.

e.g. I use OSX.

@sheerun
Copy link
Contributor

sheerun commented Jan 25, 2015

Currently it's really hard to re-produce environment for testing.. Correct libraries, correct library versions, correct paths, correct ENV..

@whitequark
Copy link
Collaborator

But it's OK to require users to reproduce the environment in some other way?

@sheerun
Copy link
Contributor

sheerun commented Jan 25, 2015

Is it a question? I tried really hard, but I can't reproduce tests on pure OSX.

@whitequark
Copy link
Collaborator

Oh... I've completely missed the fact that tests use a bunch of odd libraries. Sorry for the noise. See #31.

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

Successfully merging a pull request may close this issue.

6 participants