fan2go
fan2go copied to clipboard
error while loading shared libraries
Describe the bug
I'm not sure if its a bug or just a user error, but I copied the fan2go executable to /bin and while trying to use it this error is printed:
fan2go: error while loading shared libraries: libsensors.so.5: cannot open shared object file: No such file or directory
Desktop :
- Distro: OpenSuse Tumbleweed KDE
-
uname -a
: Linux SFX 5.15.12-1-default #1 SMP Wed Dec 29 14:50:16 UTC 2021 (375fcb8) x86_64 x86_64 x86_64 GNU/Linux -
sensors -v
: sensors version 3.6.0 with libsensors version 3.6.0 -
fan2go version
: 0.4.0
Just a guess:
Maybe you need to install libsensors4
?
Did you try? I am not going to learn how OpenSuse works for you 😄
it is/was installed
Ah sorry I didn't catch that, my bad.
Did you try compiling fan2go yourself on the target system? The gosensors integration probably needs a very very exact match of system libraries to work across different distros... only a "real" package could fix this alltogether. I will create an issue in the gosensors project, maybe there is a way to improve this.
I did this originally
now, following your suggestion, I tried to build it following instructions but I get an error.
flap@SFX:~/fan2go> make build
go build -o bin/fan2go main.go
make: go: No such file or directory
make: *** [Makefile:5: build] Error 127
To build a go program from source, you need to have the go compiler installed on your system. How to get this is different for every system so I didn't include it in the instructions, but there is most definitely a go package you can install.
Sucess!
Note that while this does fix the issue, you should be aware that the install might break because of system updates.
The only way to really fix this is with a "real" package that declares a dependency to the libsensors
package and can be automatically compiled every time it is updated.
Maybe it wasn't such a good idea to switch to the direct libsensors integration instead of parsing files manually after all...
I am closing this for now, if it comes up again, we can consider to provide an alternative to the native bindings.