-
Notifications
You must be signed in to change notification settings - Fork 263
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
Pre-built binaries not installable for ... and [email protected] (node-v57 ABI, unknown) (falling back to source compile with node-gyp) #364
Comments
Do you have full output from the install, especially any |
Hi @allenluce, here are the 2 error lines: node-pre-gyp ERR! Pre-built binaries not installable for [email protected] and [email protected] (node-v57 ABI, unknown) (falling back to source compile with node-gyp) |
I am having a similar issue with bcrypt.
It seems that the folder is not being created, rather a file with contents any random file from the download tarball is being added. Here's our node-pre-gyp config inside package.json
|
My module specifies I'm not sure why that line is in there, it showed up as part of #299 which was merged on Mar 9. Seems that 0.7.1 through 0.9.1 are affected by this. I'm not the only one to get hit by it, grpc/grpc-node#232 downgraded to 0.7.0 to avoid this problem. @springmeyer Have any idea why that |
Thanks @allenluce , I still get the issue (on Windows). I'm full-speed on a project which is using node-pre-gyp), but cannot dig into your code now unfortunately! The issue is not critical, cause I'm doing an electron-rebuild anyways, but will become critical for my users who need the nodejs client not to be recompiled. Thanks guys for looking at it! Best, |
No worries @jracle. If it becomes critical before a fix is applied, a downgrade to 0.7.0 might take care of it for you. |
@allenluce I don't, as it was added by @isaacs. But I'm in agreement that it may be the problem behind this and #356 (comment) @allenluce would you mind putting up a PR removing that line to:
I'm very limited on dev time right now, so would welcome the help. |
@springmeyer No problem. It ended up being a little more involved than just removing that line. |
Node-pre-gyp 0.7.1 through 0.9.1 have problems as detailed in mapbox/node-pre-gyp#364. The downgrade should avoid those. Once the fix is merged the version can be updated. There were problems compiling on macOS related to https://stackoverflow.com/questions/21752172/invalid-deployment-target-for-stdlib-libc-on-osx-10-8. This sets the deployment target to 10.9 which may preclude older macOS versions from using this module.
Huge thanks for diving in to fix @allenluce. Will take a look over at #371 |
@allenluce Along with #359, we were running into this issue (node giving an ENOTDIR, and our |
Apparently 0.7.1..0.9.1 have another installation issue: mapbox/node-pre-gyp#364
Thanks for the fix @allenluce! This just shipped in version |
Sounds good, thanks for the merge! As Windows is pretty painful for me to dev on, I'm hoping @AlCalzone's issue had to do with building with a different version than was in his |
I have similar issue with installing firebase with Angular 7
node-pre-gyp WARN Using needle for node-pre-gyp https download npm ERR! code ELIFECYCLE npm ERR! A complete log of this run can be found in: |
@yogbharat1 Install python2 and the entire suite of windows-build-tools (it's huge). Else, try updating |
same issue when build a docker image: > [email protected] install /app/node_modules/bcrypt
> node-pre-gyp install --fallback-to-build
node-pre-gyp WARN Pre-built binaries not installable for [email protected] and [email protected] (node-v57 ABI, musl) (falling back to source compile with node-gyp)
node-pre-gyp WARN Hit error socket hang up
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack at PythonFinder.failNoPython (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:484:19)
gyp ERR! stack at PythonFinder.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:406:16)
gyp ERR! stack at F (/usr/local/lib/node_modules/npm/node_modules/which/which.js:68:16)
gyp ERR! stack at E (/usr/local/lib/node_modules/npm/node_modules/which/which.js:80:29)
gyp ERR! stack at /usr/local/lib/node_modules/npm/node_modules/which/which.js:89:16
gyp ERR! stack at /usr/local/lib/node_modules/npm/node_modules/isexe/index.js:42:5
gyp ERR! stack at /usr/local/lib/node_modules/npm/node_modules/isexe/mode.js:8:5
gyp ERR! stack at FSReqWrap.oncomplete (fs.js:152:21)
gyp ERR! System Linux 4.9.125-linuxkit
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/app/node_modules/bcrypt/lib/binding/bcrypt_lib.node" "--module_name=bcrypt_lib" "--module_path=/app/node_modules/bcrypt/lib/binding" "--napi_version=3" "--node_abi_napi=napi"
gyp ERR! cwd /app/node_modules/bcrypt
gyp ERR! node -v v8.11.4
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/app/node_modules/bcrypt/lib/binding/bcrypt_lib.node --module_name=bcrypt_lib --module_path=/app/node_modules/bcrypt/lib/binding --napi_version=3 --node_abi_napi=napi' (1)
node-pre-gyp ERR! stack at ChildProcess.<anonymous> (/app/node_modules/bcrypt/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack at emitTwo (events.js:126:13)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:214:7)
node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:925:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
node-pre-gyp ERR! System Linux 4.9.125-linuxkit
node-pre-gyp ERR! command "/usr/local/bin/node" "/app/node_modules/bcrypt/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /app/node_modules/bcrypt
node-pre-gyp ERR! node -v v8.11.4
node-pre-gyp ERR! node-pre-gyp -v v0.10.2
node-pre-gyp ERR! not ok
Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/app/node_modules/bcrypt/lib/binding/bcrypt_lib.node --module_name=bcrypt_lib --module_path=/app/node_modules/bcrypt/lib/binding --napi_version=3 --node_abi_napi=napi' (1)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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! /root/.npm/_logs/2019-01-22T09_39_00_762Z-debug.log |
I'm not able to repro the errors seen by @yogbharat1 or @mrdulin. What OS are each of you using? Can you re-run the installation with |
@allenluce Thanks for reply. Here is my FROM mhart/alpine-node:8.11.4
ENV PORT 3200
WORKDIR /app
COPY ./package.json ./package-lock.json /app/
COPY ./ /app/
RUN apk update \
&& apk add curl python --no-cache --virtual build-dependencies build-base gcc \
&& npm i -g npm@latest \
&& npm i
HEALTHCHECK --interval=30s --timeout=30s --start-period=5s --retries=3 \
CMD curl -f http://localhost:$PORT/version || exit 1
EXPOSE ${PORT}
CMD [ "npm", "start" ] I solved this issue by adding below command: apk add curl python --no-cache --virtual build-dependencies build-base gcc |
Hi guys,
since yesterday I cannot retrieve my pre-built binaries (posted on amazon S3) using "latest" node-pre-gyp.
I suspect a regression in node-pre-gyp..
Here is what I get:
Thanks to investigate asap, this is a blocking issue.
The text was updated successfully, but these errors were encountered: