Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Install of realm-js in Raspberry PI 4 fails. #3272

Closed
RealmBot opened this issue Sep 28, 2020 · 12 comments
Closed

Install of realm-js in Raspberry PI 4 fails. #3272

RealmBot opened this issue Sep 28, 2020 · 12 comments
Assignees
@fronck
Labels
More-information-needed More information is needed to progress. The issue will close automatically in 2 weeks.

Comments

@RealmBot
Copy link
Collaborator

RealmBot commented Sep 28, 2020 •
edited
Loading

I have tried to install the realm-js drivers on a raspberry Pi Model 4. The installation fails. I amusing Ubuntu 20, 64 bit

Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux

ubuntu@ubuntu:~/sandbox/HomeAutomationRPI$ {color:#FF0000}npm install realm@beta{color}
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated [email protected]: this library is no longer supported``> [email protected] install /home/ubuntu/sandbox/HomeAutomationRPI/node_modules/realm
> node-pre-gyp install --fallback-to-build -j 8 ${npm_config_arch:+--target_arch=${npm_config_arch}}internal/modules/cjs/loader.js:638
{{ throw err;}}
{{ ^}}Error: Cannot find module '../'
{{ at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)}}
{{ at Function.Module._load (internal/modules/cjs/loader.js:562:25)}}
{{ at Module.require (internal/modules/cjs/loader.js:692:17)}}
{{ at require (internal/modules/cjs/helpers.js:25:18)}}
{{ at Object. (/home/ubuntu/sandbox/HomeAutomationRPI/node_modules/.bin/node-pre-gyp:15:20)}}
{{ at Module._compile (internal/modules/cjs/loader.js:778:30)}}
{{ at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)}}
{{ at Module.load (internal/modules/cjs/loader.js:653:32)}}
{{ at tryModuleLoad (internal/modules/cjs/loader.js:593:12)}}
{{ at Function.Module._load (internal/modules/cjs/loader.js:585:3)}}
npm WARN [email protected] requires a peer of react@* but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-native@* but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] No repository field.``npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: node-pre-gyp install --fallback-to-build -j 8 ${npm_config_arch:+--target_arch=${npm_config_arch}} `npm ERR! Exit status 1` {{npm ERR! }} `npm ERR! Failed at the [email protected] install script.` `npm ERR! This is probably not a problem with npm. There is likely additional logging output above.npm ERR! A complete log of this run can be found in: npm ERR! /home/ubuntu/.npm/_logs/2020-09-28T15_49_08_231Z-debug.log`

ubuntu@ubuntu:~/sandbox/HomeAutomationRPI$【 highlighted #FF0000 】npm install [email protected]【 end highlighted 】
npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm WARN deprecated [email protected]: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated [email protected]: this library is no longer supported

[email protected] install /home/ubuntu/sandbox/HomeAutomationRPI/node_modules/realm
node-pre-gyp install --fallback-to-build -j 8

internal/modules/cjs/loader.js:638
throw err;
^

Error: Cannot find module '../'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
at Function.Module._load (internal/modules/cjs/loader.js:562:25)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at Object. (/home/ubuntu/sandbox/HomeAutomationRPI/node_modules/.bin/node-pre-gyp:15:20)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
npm WARN [email protected] requires a peer of react@* but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of react-native@* but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] No repository field.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: node-pre-gyp install --fallback-to-build -j 8
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/ubuntu/.npm/_logs/2020-09-28T16_36_13_295Z-debug.log
@RealmBot
Copy link
Collaborator Author

➤ Jorge Imperial-Sosa commented:

Tried in 32 bit Raspbian (Debian Buster) with similar output.

@RealmBot
Copy link
Collaborator Author

➤ Lyubomir Blagoev commented:

I could not reproduce this. What version of nodejs are you using on this RPis

@RealmBot
Copy link
Collaborator Author

RealmBot commented Oct 5, 2020

➤ Jorge Imperial-Sosa commented:

Hello Lyubomir,

The version of node is 12.18.4, and raspbian is 10.4.

pi@raspberrypi:~ $ uname -a
Linux raspberrypi 5.4.51-v7l+ #1333 SMP Mon Aug 10 16:51:40 BST 2020 armv7l GNU/Linux

@RealmBot
Copy link
Collaborator Author

RealmBot commented Oct 6, 2020

➤ Jorge Imperial-Sosa commented:

ubuntu@ubuntu:/HomeAutomationRPI$ node -v
v12.14.1
ubuntu@ubuntu:/HomeAutomationRPI$ uname -a
Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux
ubuntu@ubuntu:~/HomeAutomationRPI$ cat /etc/debian_version
bullseye/sid

@kneth kneth mentioned this issue Oct 9, 2020
Merged
1 task
@kneth
Copy link
Contributor

kneth commented Oct 9, 2020

I don't have access to a RPi4 but on my RPi3 the download fails. It should fail back to building from source. I have (re)adding publishing binaries in #3328.

@RealmBot
Copy link
Collaborator Author

➤ Jorge Imperial-Sosa commented:

On another similar platform, Nvidia nano (ARM64) the build does not work either, but it seems that it is grabbing the wrong openssl.tgz

nano@nano:/mnt/HomeAutomationRPI$ npm install realm@beta
npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm WARN deprecated [email protected]: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated [email protected]: this library is no longer supported

[email protected] install /mnt/HomeAutomationRPI/node_modules/realm
node-pre-gyp install --fallback-to-build -j 8 ${npm_config_arch:+--target_arch=${npm_config_arch}}
node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp WARN Tried to download(404): https://static.realm.io/node-pre-gyp/napi-v4/realm-v10.0.0-rc.2/realm-v10.0.0-rc.2-linux-arm64.tar.gz
node-pre-gyp WARN Pre-built binaries not found for [email protected] and [email protected] (node-v72 ABI, glibc) (falling back to source compile with node-gyp)
make: Entering directory '/mnt/HomeAutomationRPI/node_modules/realm/build'
TOUCH Release/obj.target/OpenSSL.stamp
CC(target) Release/obj.target/nothing/../node-addon-api/nothing.o
ACTION binding_gyp_vendored_realm_target_download_realm /mnt/HomeAutomationRPI/node_modules/realm/vendor/realm-linux-arm64
TOUCH Release/obj.target/scripts.stamp
AR(target) Release/obj.target/../node-addon-api/nothing.a
Resolved requirements: {
SYNC_SERVER_FOLDER: 'sync',
SYNC_ARCHIVE: 'realm-sync-Release-v10.0.0-beta.14-Linux-devel.tar.gz',
OPENSSL: 'https://static.realm.io/downloads/openssl/1.1.1b/Linux/x86_64/openssl.tgz',
CORE_SERVER_FOLDER: 'core',
CORE_ARCHIVE: 'realm-core-Release-v10.0.0-beta.9-Linux-devel.tar.gz'
}

@RealmBot
Copy link
Collaborator Author

➤ Kenneth Geisshirt commented:

We do not support nvidia nano. Currently we are building for armhf ( https://stackoverflow.com/questions/37790029/what-is-difference-between-arm64-and-armhf ) only.

@ianpward
Copy link

@kneth Is this 32bit or 64bit architecture issue? Or am I reading this incorrectly

@RealmBot
Copy link
Collaborator Author

➤ Kenneth Geisshirt commented:

True, we only build for 32 bit ARM (with hardware floating-pointing support).

@fronck
Copy link

fronck commented Oct 22, 2020 •
edited
Loading

I have verified that the install now works on a RPi 3/Ubuntu 20.04 LTS/armv7.

@sync-by-unito
Copy link

sync-by-unito bot commented Oct 23, 2020

➤ Lyubomir Blagoev commented:

[~jorge.imperial] 

I couldn't repro it on PI 4 with realm v10.0.1 (latest version)

It downloads the binary from remote by default which does not require a build

I have forced npm to build from source when installing using npm install -buildfrom-source which also succeeds.

!realm.v10.jpeg!

@fronck fronck added the More-information-needed More information is needed to progress. The issue will close automatically in 2 weeks. label Nov 2, 2020
@no-response
Copy link

no-response bot commented Nov 18, 2020

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@no-response no-response bot closed this as completed Nov 18, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@fronck fronck

Labels
More-information-needed More information is needed to progress. The issue will close automatically in 2 weeks.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@kneth @ianpward @blagoev @fronck @RealmBot