-
Notifications
You must be signed in to change notification settings - Fork 32
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
Cannot open shared object #25
Comments
@MarioRuiz I think this might be a duplicate of #22 Before getting into that thread though, check that your user is a member of the gpio group. |
I'm running into the same problem:
The "deploy" user has access to the gpio stuff. |
I have the same issue here, rpi 3B+, ruby-2.6.6, rpi_gpio-0.5.0
So it is no permission issue. Any other ideas? |
I'm running into the same trouble here. After moving to a newer version of Raspberry Pi OS (on the same hardware), my Ruby code with rpi_gpio stopped working. Ruby 2.7.4p191 here, on a RPi 3B+. The gem installation works without errors. require-ing the gem then fails with "cannot open shared object file: No such file or directory", even though rpi_gpio.so exists under exactly the path stated in the error message. Exactly as for @martini above. Running as root doesn't make a difference. Has anyone made progress in that regard already? Any hints? (Edited: It's actually a RPi 3B+, not a RPi 4 as stated in my original post. I have too many RPis, it appears, if it's getting so difficult to tell them apart. Shame on me. ;-P ) |
It really is a shame there is no way to work around this issue and we're getting nothing but the sound of crickets from the maintainer... Looks like I'll have to use the go gpio port to generate an executable to perform the gpio stuff and call that from my Ruby program. Super annoying. |
Coming into the same issue and noticed that
So maybe it needs Ruby 2.7.0 installed? I'm attempting that and will report back |
Yeah that fixes it. For anyone else arriving here from google:
Interestingly I still see the missing file in |
In my case, libruby file name was different. so I created symlinks.
|
it will work |
Getting next error on a rpi 3B+
The text was updated successfully, but these errors were encountered: