-
Notifications
You must be signed in to change notification settings - Fork 74
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
Binary Path in Release 0.16 is wrong #85
Comments
Could you please use the node-rfc@next because node-rfc is not supported on node 10. |
When using node-rfc@next the
|
Could you please share the Linux version/release you are using? Is it a docker image and which one? |
It's a Docker-Container running on Docker version 18.09.5. Here's my first draft of the Dockerfile:
The js file I try to execute afterwards is just a connection attempt which worked when using node-rfc (0.16):
|
docker node images are based on older GLIBC versions and node-rfc must be built from source on them (see #35). The In the meantime, attached sapnwrfc.node should help, just unpack and |
The |
Perfect, thx. Will try it asap. |
Fixed in rc10. |
@bsrdjan : I just tried to install rc10 within my Docker-Container: When calling my connection-function I still receive the error
When building from source it works |
When performing a "npm install node-rfc" I receive the following Error:
The Binary Path provided in package.json is not valid anymore.
You should take "https://github.com/SAP/node-rfc/releases/tag/" instead of "https://github.com/sap/node-rfc/releases/download/"
The text was updated successfully, but these errors were encountered: