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.

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

Mismatch version between nodejs and nodejs headers.tar.gz #1680

Closed
f-w opened this issue Feb 27, 2019 · 1 comment
Closed

Mismatch version between nodejs and nodejs headers.tar.gz #1680

f-w opened this issue Feb 27, 2019 · 1 comment

Comments

@f-w
Copy link

f-w commented Feb 27, 2019

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

> [email protected] install /opt/app-root/src/node_modules/lame
> node-gyp rebuild

gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | 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>

File /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.

@rvagg
Copy link
Member

rvagg commented Jun 20, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants