[SOLVED] Gzweb build error depend Node.js version when running ./update_nrp build all

#1

Hello everyone,

I’m installing NRP from source on Ubuntu 18.04.
The build command:./update_nrp build all stoped at gzweb build like below.

-------------------------
gzweb
-------------------------
You must use node v0.10 or use nvm and install v0.10 (ie. nvm install 0.10)
GZBRIDGE BUILD ERROR

Here is a versions of Node.js and nvm that seem same as of NRP on Docker.

user1@7014cdac9b5e:~/Documents/NRP/user-scripts$ node -v
v8.17.0
user1@7014cdac9b5e:~/Documents/NRP/user-scripts$ nvm ls
-> v8.17.0
default -> 8 (-> v8.17.0)
node -> stable (-> v8.17.0) (default)
stable -> 8.17 (-> v8.17.0) (default)
iojs -> N/A (default)
lts/* -> lts/erbium (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0
lts/dubnium -> v10.22.1 (-> N/A)
lts/erbium -> v12.18.4 (-> N/A)

Would you give me any suggestion to solve this problem?

Best regards,
Yanbaru

[SOLVED] frontendStateMachineEditor CHECKOUT ERROR when running ./update_nrp build
#2

Hi,

I don’t see the issue here as well. Did you upgrade from Ubuntu 16 or install a fresh 18?

Axel

#3

Dear vonarnim

Thank you for your reply.
I install with fresh Ubuntu 18.04.

Best regards,
Yanbaru

#4

Try to add node 0.10: nvm install 0.10 but keep v8 as the default.

#5

Dear vonarnim

I tried your suggestions, and here is the result of them.

1. install Node.js v0.10 (Ineffective)

user1@7014cdac9b5e:~/Documents/NRP/user-scripts$ nvm install 0.10
Downloading and installing node v0.10.48...
Downloading https://nodejs.org/dist/v0.10.48/node-v0.10.48-linux-x64.tar.xz...
############################################################################################################################################################### 100.0%
Computing checksum with sha256sum
Checksums matched!
Now using node v0.10.48 (npm v2.15.1)
user1@7014cdac9b5e:~/Documents/NRP/user-scripts$ node -v
v0.10.48
user1@7014cdac9b5e:~/Documents/NRP/user-scripts$ nvm ls
-> v0.10.48
v8.17.0
default -> 8 (-> v8.17.0)
node -> stable (-> v8.17.0) (default)
stable -> 8.17 (-> v8.17.0) (default)
iojs -> N/A (default)
lts/* -> lts/erbium (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0
lts/dubnium -> v10.22.1 (-> N/A)
lts/erbium -> v12.18.4 (-> N/A)

this caused another problem before reaching gzweb build step.

ExDFrontend
-----------------------
・
npm ERR! Linux 4.19.76-linuxkit
npm ERR! argv "/home/user1/.nvm/v0.10.48/bin/node" "/home/user1/.nvm/v0.10.48/bin/npm" "dedupe"
npm ERR! node v0.10.48
npm ERR! npm v2.15.1
npm ERR! code EPEERINVALID
npm ERR! peerinvalid The package acorn@5.7.4 does not satisfy its siblings' peerDependencies requirements!
npm ERR! Please include the following file with any support request:
npm ERR! /home/user1/Documents/NRP/ExDFrontend/npm-debug.log
ExDFrontend INSTALL ERROR

Error: npm ERR! EPEERINVALID was discussed here, but npm upgrade -g doesn’t solve the problem.

2. recloning gzweb directory (effective)
I was rerun with an environment that is before first attempting ./update_nrp build all command.

cd $HBP
sudo rm -r gzweb
cd $HBP/user-scripts
./clone-all-repos
./update_nrp build all

I think this solved the problem with building gzweb!!
Unfortunately,./update_nrp build all stoped at frontendStateMachineEditor build step, so I’ll post it as new topic.

I appreciate your supports.

Best regards,
Yanbaru

#6

Dear Yanbaru

As I understand from your other post, this issue with gzweb is fixed.