You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Output excerpt of npm i lame. Notice node-gyp is expecting v10.15.0 of headers.tar.gz, while nodejs is on v10.15.1
> lame@1.2.4 install /opt/app-root/src/node_modules/lame
> node-gyp rebuild
gyp info it worked if it ends with ok
gyp info using node-gyp@3.8.0
gyp info using node@10.15.1 | linux | x64
gyp ERR! UNCAUGHT EXCEPTION
gyp ERR! stack Error: ENOENT: no such file or directory, open '/usr/share/node/node-v10.15.0-headers.tar.gz'
gyp ERR! System Linux 4.9.93-boot2docker
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules.bundled/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /opt/app-root/src/node_modules/lame
gyp ERR! node -v v10.15.1
gyp ERR! node-gyp -v v3.8.0
gyp ERR! This is a bug in `node-gyp`.
gyp ERR! Try to update node-gyp and file an Issue if it does not help:
gyp ERR! <https://github.com/nodejs/node-gyp/issues>
Sorry we haven't been able to help out @f-w, I hope you've managed to get this sorted out? tbh I have no idea why it's looking for anything in /usr/share/node/, it normally gets header tarballs from nodejs.org and puts them in ~/.node-gyp unpacked. My guess is that the openshift container is configured a bit funky and is forcing this mismatch, maybe some environment variable that is telling node-gyp where to get headers from.
Output excerpt of
npm i lame
. Notice node-gyp is expecting v10.15.0 of headers.tar.gz, while nodejs is on v10.15.1File /usr/share/node/node-v10.15.0-headers.tar.gz doesn't exist, however /usr/share/node/node-v10.15.1-headers.tar.gz does.
The text was updated successfully, but these errors were encountered: