question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The npm install --save sonus fails with errors. The first error seems to be - its not able to download the Snowboy package. We can install Snowboy manually or change the URL in the script… But I don’t know from where I can change the script. Can anyone help please.

node-pre-gyp ERR! Tried to download(403): https://snowboy-release-node.s3-us-west-2.amazonaws.com/snowboy/v1.2.0/Release/snowboy-v1.2.0-node-v59-linux-arm.tar.gz node-pre-gyp ERR! Pre-built binaries not found for snowboy@1.2.0 and node@9.3.0 (node-v59 ABI, glibc) (falling back to source compile with node-gyp) make: Entering directory ‘/home/pi/node_modules/snowboy/build’ CXX(target) Release/obj.target/snowboy/swig/Node/snowboy.o SOLINK_MODULE(target) Release/obj.target/snowboy.node /usr/bin/ld: cannot find -lcblas collect2: error: ld returned 1 exit status snowboy.target.mk:131: recipe for target ‘Release/obj.target/snowboy.node’ failed make: *** [Release/obj.target/snowboy.node] Error 1 make: Leaving directory ‘/home/pi/node_modules/snowboy/build’ gyp ERR! build error gyp ERR! stack Error: make failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:258:23) gyp ERR! stack at ChildProcess.emit (events.js:159:13) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:12) gyp ERR! System Linux 4.9.59-v7+ gyp ERR! command “/usr/bin/node” “/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js” “build” “–fallback-to-build” “–module=/home/pi/node_modules/snowboy/lib/node/binding/Release/node-v59-linux-arm/snowboy.node” “–module_name=snowboy” “–module_path=/home/pi/node_modules/snowboy/lib/node/binding/Release/node-v59-linux-arm” gyp ERR! cwd /home/pi/node_modules/snowboy gyp ERR! node -v v9.3.0 gyp ERR! node-gyp -v v3.6.2 gyp ERR! not ok node-pre-gyp ERR! build error node-pre-gyp ERR! stack Error: Failed to execute ‘/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/pi/node_modules/snowboy/lib/node/binding/Release/node-v59-linux-arm/snowboy.node --module_name=snowboy --module_path=/home/pi/node_modules/snowboy/lib/node/binding/Release/node-v59-linux-arm’ (1) node-pre-gyp ERR! stack at ChildProcess.<anonymous> (/home/pi/node_modules/snowboy/node_modules/node-pre-gyp/lib/util/compile.js:83:29) node-pre-gyp ERR! stack at ChildProcess.emit (events.js:159:13) node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:943:16) node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5) node-pre-gyp ERR! System Linux 4.9.59-v7+ node-pre-gyp ERR! command “/usr/bin/node” “/home/pi/node_modules/snowboy/node_modules/.bin/node-pre-gyp” “install” “–fallback-to-build” node-pre-gyp ERR! cwd /home/pi/node_modules/snowboy node-pre-gyp ERR! node -v v9.3.0 node-pre-gyp ERR! node-pre-gyp -v v0.6.39 node-pre-gyp ERR! not ok Failed to execute ‘/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/pi/node_modules/snowboy/lib/node/binding/Release/node-v59-linux-arm/snowboy.node --module_name=snowboy --module_path=/home/pi/node_modules/snowboy/lib/node/binding/Release/node-v59-linux-arm’ (1) npm WARN enoent ENOENT: no such file or directory, open ‘/home/pi/package.json’ npm WARN pi No description npm WARN pi No repository field. npm WARN pi No README data npm WARN pi No license field.

npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! snowboy@1.2.0 install: node-pre-gyp install --fallback-to-build npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the snowboy@1.2.0 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/pi/.npm/_logs/2017-12-22T06_59_42_257Z-debug.log

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
evancohencommented, Dec 23, 2017

Guessing this is because you are using Node 9.x - while this isn’t technically supported yet, you should be able to build the native binary for yourself by running the following before npm install:

sudo apt-get install libmagic-dev libatlas-base-dev
npm install -g nan
0reactions
evancohencommented, Mar 10, 2019

Guessing that this issue has been resolved since @ag-ni never got back to me, if not please feel free to re-open.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Get help with Windows upgrade and installation errors
See some of the most common upgrade and installation errors for Windows 10 and ... Look for the update that wasn't installed, note...
Read more >
[SOLVED] Windows 10 Installation Has Failed - Driver Easy
1: Remove the peripheral devices · 2: Clear an attribute of $WINDOWS.~BT installation folder · 3: Uninstall the language pack · 4: Rebuild...
Read more >
How to Fix "Windows 10 Installation has Failed" Error? - Appuals
How to Fix “Windows 10 Installation has Failed” Error? · 1. Meet the minimum requirements · 2. Remove all non-essential peripherals · 3....
Read more >
4 Solutions to Fix Windows 10/11 Installation Has Failed
4 Solutions to Fix the "Windows 10/11 installation has failed" Error · Solution 1: Run a Clean Boot Installation · Solution 2: Create...
Read more >
Windows 10 Installation Has Failed [Easily FIXED]
How do I fix Windows 10 installation failed? · 1. Unplug all peripheral devices · 2. Uninstall the language pack · 3. Uninstall...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found