You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I realise this library is not very actively maintained, but it's currently still a dependency of the zwave-adapter for WebThings Gateway.
With the patch from #2647 applied we've found it is still working, at least on an x64 architecture.
The problem we're having is when trying to use the library on a Raspberry Pi, specifically a Raspberry Pi 4 model B. After building the library for the armv7l architecture OpenZWave will not run. It fails to start with the error below:
node_modules/openzwave-shared/build/Release/openzwave_shared.node: ELF load command address/offset not properly aligned
A member of our community suggested that the problem could be that the library was being compiled for 4K pages, but being run on a system with 16K pages. We therefore tried modifying Makefile to set LDFLAGS in an effort to support both, but it doesn't appear to have worked.
I'm not a C++ developer so am out of my depth on this. Is anyone able to recommend how to fix this issue?
Edit: I should have mentioned we're using the openzwave-shared npm wrapper.
The text was updated successfully, but these errors were encountered:
I realise this library is not very actively maintained, but it's currently still a dependency of the zwave-adapter for WebThings Gateway.
With the patch from #2647 applied we've found it is still working, at least on an x64 architecture.
The problem we're having is when trying to use the library on a Raspberry Pi, specifically a Raspberry Pi 4 model B. After building the library for the armv7l architecture OpenZWave will not run. It fails to start with the error below:
A member of our community suggested that the problem could be that the library was being compiled for 4K pages, but being run on a system with 16K pages. We therefore tried modifying
Makefile
to setLDFLAGS
in an effort to support both, but it doesn't appear to have worked.I'm not a C++ developer so am out of my depth on this. Is anyone able to recommend how to fix this issue?
Edit: I should have mentioned we're using the openzwave-shared npm wrapper.
The text was updated successfully, but these errors were encountered: