Build error when installing bip32 on Azure node.js service
up vote
0
down vote
favorite
I'm trying to deploy a node.js app on Azure. Simply moving the node-modules from my mac and running the url results in
Error: \?D:homesitewwwrootnode_modulesscryptbuildReleasescrypt.node is not a valid Win32 application.
So I decided to install the nodules directly on the machine. I ssh'd to it and started installing packages. A couple worked well but when attempting to install bip32 it fails with the following stack.
Any ideas?
D:homesitewwwroot
gyp ERR! build error
gyp ERR! stack Error: `msbuild` failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (D:Program Files (x86)npm6.1.0node_modulesnpmnode_modulesnode-gyplibbuild.js:258:23)
gyp ERR! stack at ChildProcess.emit (events.js:182:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:237:12)
gyp ERR! System Windows_NT 10.0.14393
gyp ERR! command "D:\Program Files (x86)\nodejs\10.6.0\node.exe" "D:\Program Files (x86)\npm\6.1.0\node_modules\npm\node_modules\node-
gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd D:homesitewwwrootnode_modulestiny-secp256k1
gyp ERR! node -v v10.6.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm WARN Invalid version: "0.2"
npm WARN wwwroot No description
npm WARN wwwroot No repository field.
npm WARN wwwroot No README data
npm WARN wwwroot No license field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! tiny-secp256k1@1.0.1 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the tiny-secp256k1@1.0.1 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! D:localAppDatanpm-cache_logs2018-11-11T12_02_52_844Z-debug.log
node.js
azure npm asked Nov 11 at 12:15
Eddy
1,32443656
add a comment |
up vote
0
down vote
favorite
I'm trying to deploy a node.js app on Azure. Simply moving the node-modules from my mac and running the url results in
Error: \?D:homesitewwwrootnode_modulesscryptbuildReleasescrypt.node is not a valid Win32 application.
So I decided to install the nodules directly on the machine. I ssh'd to it and started installing packages. A couple worked well but when attempting to install bip32 it fails with the following stack.
Any ideas?
D:homesitewwwroot
gyp ERR! build error
gyp ERR! stack Error: `msbuild` failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (D:Program Files (x86)npm6.1.0node_modulesnpmnode_modulesnode-gyplibbuild.js:258:23)
gyp ERR! stack at ChildProcess.emit (events.js:182:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:237:12)
gyp ERR! System Windows_NT 10.0.14393
gyp ERR! command "D:\Program Files (x86)\nodejs\10.6.0\node.exe" "D:\Program Files (x86)\npm\6.1.0\node_modules\npm\node_modules\node-
gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd D:homesitewwwrootnode_modulestiny-secp256k1
gyp ERR! node -v v10.6.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm WARN Invalid version: "0.2"
npm WARN wwwroot No description
npm WARN wwwroot No repository field.
npm WARN wwwroot No README data
npm WARN wwwroot No license field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! tiny-secp256k1@1.0.1 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the tiny-secp256k1@1.0.1 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! D:localAppDatanpm-cache_logs2018-11-11T12_02_52_844Z-debug.log
node.js
azure npm asked Nov 11 at 12:15
Eddy
1,32443656
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm trying to deploy a node.js app on Azure. Simply moving the node-modules from my mac and running the url results in
Error: \?D:homesitewwwrootnode_modulesscryptbuildReleasescrypt.node is not a valid Win32 application.
So I decided to install the nodules directly on the machine. I ssh'd to it and started installing packages. A couple worked well but when attempting to install bip32 it fails with the following stack.
Any ideas?
D:homesitewwwroot
gyp ERR! build error
gyp ERR! stack Error: `msbuild` failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (D:Program Files (x86)npm6.1.0node_modulesnpmnode_modulesnode-gyplibbuild.js:258:23)
gyp ERR! stack at ChildProcess.emit (events.js:182:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:237:12)
gyp ERR! System Windows_NT 10.0.14393
gyp ERR! command "D:\Program Files (x86)\nodejs\10.6.0\node.exe" "D:\Program Files (x86)\npm\6.1.0\node_modules\npm\node_modules\node-
gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd D:homesitewwwrootnode_modulestiny-secp256k1
gyp ERR! node -v v10.6.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm WARN Invalid version: "0.2"
npm WARN wwwroot No description
npm WARN wwwroot No repository field.
npm WARN wwwroot No README data
npm WARN wwwroot No license field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! tiny-secp256k1@1.0.1 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the tiny-secp256k1@1.0.1 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! D:localAppDatanpm-cache_logs2018-11-11T12_02_52_844Z-debug.log
node.js
azure npm asked Nov 11 at 12:15
Eddy
1,32443656
I'm trying to deploy a node.js app on Azure. Simply moving the node-modules from my mac and running the url results in
Error: \?D:homesitewwwrootnode_modulesscryptbuildReleasescrypt.node is not a valid Win32 application.
So I decided to install the nodules directly on the machine. I ssh'd to it and started installing packages. A couple worked well but when attempting to install bip32 it fails with the following stack.
Any ideas?
D:homesitewwwroot
gyp ERR! build error
gyp ERR! stack Error: `msbuild` failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (D:Program Files (x86)npm6.1.0node_modulesnpmnode_modulesnode-gyplibbuild.js:258:23)
gyp ERR! stack at ChildProcess.emit (events.js:182:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:237:12)
gyp ERR! System Windows_NT 10.0.14393
gyp ERR! command "D:\Program Files (x86)\nodejs\10.6.0\node.exe" "D:\Program Files (x86)\npm\6.1.0\node_modules\npm\node_modules\node-
gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd D:homesitewwwrootnode_modulestiny-secp256k1
gyp ERR! node -v v10.6.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm WARN Invalid version: "0.2"
npm WARN wwwroot No description
npm WARN wwwroot No repository field.
npm WARN wwwroot No README data
npm WARN wwwroot No license field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! tiny-secp256k1@1.0.1 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the tiny-secp256k1@1.0.1 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! D:localAppDatanpm-cache_logs2018-11-11T12_02_52_844Z-debug.log
node.js
azure npm node.js
azure npm asked Nov 11 at 12:15
Eddy
1,32443656
asked Nov 11 at 12:15
Eddy
1,32443656
asked Nov 11 at 12:15
Eddy
1,32443656
asked Nov 11 at 12:15
Eddy
1,32443656
asked Nov 11 at 12:15
Eddy
1,32443656
1,32443656
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
-1
down vote
Your build fails because it can not build the tiny-secp256k1 module, which requires secp256k1 native C module.
Solution could be to use secp256k1-node npm module instead. Take a look the windows specific installation notes in the linked repo.
Or simply install the required secp256k1 native C dependency.
answered Nov 11 at 12:50
lependu
659314
tiny-secp256k1is installed as part of thebip32install, which obviously is out of my control. So I can't use your solution.
– Eddy
Nov 11 at 13:00
You asked for the reason, not for the solution. But I edited my answer :)
– lependu
Nov 11 at 13:14
This is supposed to be a managed service. Having to install packages myself is really not inspiring confidence. Anyway. Which type of machine do I get, when creating the Web App? I moved the entire node-modules folder from another windows machine, but I still get this error:Error: \?D:homesitewwwrootnode_modulesscryptbuildReleasescrypt.node is not a valid Win32 application.
– Eddy
Nov 11 at 14:09
Sorry man i can't install the required dependencies instead of you. Please, be aware that I do this in my spare time for free. So maybe you need to pay some professional support service if this is not enough for you. You can find all the required information following the links in my answer.
– lependu
Nov 11 at 14:27
Sorry, I thought you were a support engineer. The point I was trying to make is that I could install the dependencies myself but a managed service should be able to handle this stuff. Even better, if done correctly it would install the modules for you, not a big deal to create a script to do it.
– Eddy
Nov 11 at 15:31
|
show 2 more comments
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
-1
down vote
Your build fails because it can not build the tiny-secp256k1 module, which requires secp256k1 native C module.
Solution could be to use secp256k1-node npm module instead. Take a look the windows specific installation notes in the linked repo.
Or simply install the required secp256k1 native C dependency.
answered Nov 11 at 12:50
lependu
659314
tiny-secp256k1is installed as part of thebip32install, which obviously is out of my control. So I can't use your solution.
– Eddy
Nov 11 at 13:00
You asked for the reason, not for the solution. But I edited my answer :)
– lependu
Nov 11 at 13:14
This is supposed to be a managed service. Having to install packages myself is really not inspiring confidence. Anyway. Which type of machine do I get, when creating the Web App? I moved the entire node-modules folder from another windows machine, but I still get this error:Error: \?D:homesitewwwrootnode_modulesscryptbuildReleasescrypt.node is not a valid Win32 application.
– Eddy
Nov 11 at 14:09
Sorry man i can't install the required dependencies instead of you. Please, be aware that I do this in my spare time for free. So maybe you need to pay some professional support service if this is not enough for you. You can find all the required information following the links in my answer.
– lependu
Nov 11 at 14:27
Sorry, I thought you were a support engineer. The point I was trying to make is that I could install the dependencies myself but a managed service should be able to handle this stuff. Even better, if done correctly it would install the modules for you, not a big deal to create a script to do it.
– Eddy
Nov 11 at 15:31
|
show 2 more comments
up vote
-1
down vote
Your build fails because it can not build the tiny-secp256k1 module, which requires secp256k1 native C module.
Solution could be to use secp256k1-node npm module instead. Take a look the windows specific installation notes in the linked repo.
Or simply install the required secp256k1 native C dependency.
answered Nov 11 at 12:50
lependu
659314
tiny-secp256k1is installed as part of thebip32install, which obviously is out of my control. So I can't use your solution.
– Eddy
Nov 11 at 13:00
You asked for the reason, not for the solution. But I edited my answer :)
– lependu
Nov 11 at 13:14
This is supposed to be a managed service. Having to install packages myself is really not inspiring confidence. Anyway. Which type of machine do I get, when creating the Web App? I moved the entire node-modules folder from another windows machine, but I still get this error:Error: \?D:homesitewwwrootnode_modulesscryptbuildReleasescrypt.node is not a valid Win32 application.
– Eddy
Nov 11 at 14:09
Sorry man i can't install the required dependencies instead of you. Please, be aware that I do this in my spare time for free. So maybe you need to pay some professional support service if this is not enough for you. You can find all the required information following the links in my answer.
– lependu
Nov 11 at 14:27
Sorry, I thought you were a support engineer. The point I was trying to make is that I could install the dependencies myself but a managed service should be able to handle this stuff. Even better, if done correctly it would install the modules for you, not a big deal to create a script to do it.
– Eddy
Nov 11 at 15:31
|
show 2 more comments
up vote
-1
down vote
up vote
-1
down vote
Your build fails because it can not build the tiny-secp256k1 module, which requires secp256k1 native C module.
Solution could be to use secp256k1-node npm module instead. Take a look the windows specific installation notes in the linked repo.
Or simply install the required secp256k1 native C dependency.
answered Nov 11 at 12:50
lependu
659314
Your build fails because it can not build the tiny-secp256k1 module, which requires secp256k1 native C module.
Solution could be to use secp256k1-node npm module instead. Take a look the windows specific installation notes in the linked repo.
Or simply install the required secp256k1 native C dependency.
answered Nov 11 at 12:50
lependu
659314
edited Nov 11 at 13:14
answered Nov 11 at 12:50
lependu
659314
answered Nov 11 at 12:50
lependu
659314
answered Nov 11 at 12:50
lependu
659314
659314
tiny-secp256k1is installed as part of thebip32install, which obviously is out of my control. So I can't use your solution.
– Eddy
Nov 11 at 13:00
You asked for the reason, not for the solution. But I edited my answer :)
– lependu
Nov 11 at 13:14
This is supposed to be a managed service. Having to install packages myself is really not inspiring confidence. Anyway. Which type of machine do I get, when creating the Web App? I moved the entire node-modules folder from another windows machine, but I still get this error:Error: \?D:homesitewwwrootnode_modulesscryptbuildReleasescrypt.node is not a valid Win32 application.
– Eddy
Nov 11 at 14:09
Sorry man i can't install the required dependencies instead of you. Please, be aware that I do this in my spare time for free. So maybe you need to pay some professional support service if this is not enough for you. You can find all the required information following the links in my answer.
– lependu
Nov 11 at 14:27
Sorry, I thought you were a support engineer. The point I was trying to make is that I could install the dependencies myself but a managed service should be able to handle this stuff. Even better, if done correctly it would install the modules for you, not a big deal to create a script to do it.
– Eddy
Nov 11 at 15:31
|
show 2 more comments
tiny-secp256k1is installed as part of thebip32install, which obviously is out of my control. So I can't use your solution.
– Eddy
Nov 11 at 13:00
You asked for the reason, not for the solution. But I edited my answer :)
– lependu
Nov 11 at 13:14
This is supposed to be a managed service. Having to install packages myself is really not inspiring confidence. Anyway. Which type of machine do I get, when creating the Web App? I moved the entire node-modules folder from another windows machine, but I still get this error:Error: \?D:homesitewwwrootnode_modulesscryptbuildReleasescrypt.node is not a valid Win32 application.
– Eddy
Nov 11 at 14:09
Sorry man i can't install the required dependencies instead of you. Please, be aware that I do this in my spare time for free. So maybe you need to pay some professional support service if this is not enough for you. You can find all the required information following the links in my answer.
– lependu
Nov 11 at 14:27
Sorry, I thought you were a support engineer. The point I was trying to make is that I could install the dependencies myself but a managed service should be able to handle this stuff. Even better, if done correctly it would install the modules for you, not a big deal to create a script to do it.
– Eddy
Nov 11 at 15:31
tiny-secp256k1 is installed as part of the bip32 install, which obviously is out of my control. So I can't use your solution.– Eddy
Nov 11 at 13:00
tiny-secp256k1 is installed as part of the bip32 install, which obviously is out of my control. So I can't use your solution.– Eddy
Nov 11 at 13:00
You asked for the reason, not for the solution. But I edited my answer :)
– lependu
Nov 11 at 13:14
You asked for the reason, not for the solution. But I edited my answer :)
– lependu
Nov 11 at 13:14
This is supposed to be a managed service. Having to install packages myself is really not inspiring confidence. Anyway. Which type of machine do I get, when creating the Web App? I moved the entire node-modules folder from another windows machine, but I still get this error:
Error: \?D:homesitewwwrootnode_modulesscryptbuildReleasescrypt.node is not a valid Win32 application.– Eddy
Nov 11 at 14:09
This is supposed to be a managed service. Having to install packages myself is really not inspiring confidence. Anyway. Which type of machine do I get, when creating the Web App? I moved the entire node-modules folder from another windows machine, but I still get this error:
Error: \?D:homesitewwwrootnode_modulesscryptbuildReleasescrypt.node is not a valid Win32 application.– Eddy
Nov 11 at 14:09
Sorry man i can't install the required dependencies instead of you. Please, be aware that I do this in my spare time for free. So maybe you need to pay some professional support service if this is not enough for you. You can find all the required information following the links in my answer.
– lependu
Nov 11 at 14:27
Sorry man i can't install the required dependencies instead of you. Please, be aware that I do this in my spare time for free. So maybe you need to pay some professional support service if this is not enough for you. You can find all the required information following the links in my answer.
– lependu
Nov 11 at 14:27
Sorry, I thought you were a support engineer. The point I was trying to make is that I could install the dependencies myself but a managed service should be able to handle this stuff. Even better, if done correctly it would install the modules for you, not a big deal to create a script to do it.
– Eddy
Nov 11 at 15:31
Sorry, I thought you were a support engineer. The point I was trying to make is that I could install the dependencies myself but a managed service should be able to handle this stuff. Even better, if done correctly it would install the modules for you, not a big deal to create a script to do it.
– Eddy
Nov 11 at 15:31
|
show 2 more comments
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53248659%2fbuild-error-when-installing-bip32-on-azure-node-js-service%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
