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 'libglib-2.0.so.0.so' #212
Comments
Hello @linkyndy, Well, that looks bad: I'll see if I can reproduce the problem in a docker container. |
Yes, I see this in a container as well: https://github.com/jcupitt/docker-builds/blob/master/ruby-vips-alpine/Dockerfile Here's what seems to be happening:
https://github.com/ffi/ffi/blob/master/lib/ffi/library.rb#L50 So it looks like Alpine is not GNU enough for ffi, I think. Looking at https://github.com/ffi/ffi/blob/master/lib/ffi/platform.rb#L91 IS_GNU = defined?(GNU_LIBC) So I think this is a Ruby ffi bug: they should not add that extra suffix on Alpine. |
What do you think @linkyndy? We could try opening an issue on ruby ffi. Perhaps they need an |
I tested with both |
I think it only worked on Alpine with ruby-vips 2.0.15 if you had the Without that package, there's no |
Both gem versions were tested with the following installed on an Alpine container:
So, I would assume the dependencies were the same 🤔 |
|
I made an issue here: ffi/ffi#727 |
Thanks a lot @jcupitt for your very quick action! Looking forward to this being resolved 😊 |
The very helpful @larskanis has changed ffi to hopefully fix this. I'll close -- please open a new issue if you run into more problems. |
ffi-1.11.2 should fix this issue. |
Hello,
I've tried using the
2.0.16
version of this gem on Ruby2.5.5
(combined with libvips8.8.3
on an Alpine Docker container, if it helps) and I get the following error:I assume it has to do with the latest changes with regards to generating libnames.
The text was updated successfully, but these errors were encountered: