-
Notifications
You must be signed in to change notification settings - Fork 258
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
Error: Could not locate the bindings file. #253
Comments
I also got the same issue. |
I ran into the same error on Fedora 20:
After rebuilding it worked fine for me, though:
I can paste the |
Likely a node-gyp issue or possibly some permissions issue. Do not think this is libxmljs at fault here. |
Hi , we see this issue, is there any plan to fix it in libxmljs without the workaround. |
I was able to get this to work by reverting commit: e610388 As an informational point, the module compiled and worked fine on my Mac workstation. When I deployed it to an Ubuntu box (running 14.04) I received the same message.
Doing a find yielded:
I edited the file in that commit and removed the two lines and did an npm rebuild. After that, things ran as expected without errors. It is likely an error somewhere else as things worked on Mac but not on Ubuntu, but if you ever did want to investigate why people are starting to have problems on some systems, that might be a good place to start. For now I guess I endure the headache of having to fiddle with that to get it working. |
Additional Info:
You'll note that build/Release/xmljs.node is one of the paths listed in the initial error message. |
…ddons" Per libxmljs#253 (comment) This reverts commit e610388.
This is the only solution I could get working: gwicke@7e1ceaf |
Hi, When will the fix be available within the official version? thanks, |
I can't use the npm distributed version of libxmljs either because of this. gwicke/libxmljs@7e1ceaf also fixes it for me. |
Still can't use libxmljs from npm. Same problem. I had to do this to work around it:
I'm on Debian Sid (unstable). |
I had this problem with the deasync and Node 5.6.0. Solved it with |
FWIW, this is still happening for me:
|
…ddons" Per libxmljs#253 (comment) This reverts commit e610388.
Is anyone still affected by this issue? |
I'm running into it now. Tried on Windows, current versions of Node, NPM, and libxmljs. |
Ran into this issue today as well. Thanks for the above context and solutions everyone! gwicke@7e1ceaf fixed this for me.
And a rebuild is then necessary. |
I am facing this issue as well. My OS is based on Ubuntu (which is based on Debian) lsb_release -a
node --version && npm --version
"libxmljs": "^0.18.4", Edit: rm node_modules/ && yarn # (npm install) gives me:
Edit 2: npm rebuild --update-binary gives me:
Edit 3: Relates to #463. Edit 4: I updated my NodeJS/NPM... node --version && npm --version
Now instead of This is tiring. |
Myself as well now running in WSL (Ubuntu on Windows 10). I've also tried To borrow from pedzed's wonderful format......
Not sure if that error is more about how this project works in yarn, or if it's more about the issue I'm facing (I didn't know what yarn did 10 minutes ago and an hour ago I was thinking about putting up my own npm proxy/cache) :) UPDATE: I think that yarn error has more to do with a totally different (xslt related) module being used inside my grunt task which is called by the postinstall script. |
I also had this issue when building my project with libxmljs 0.18.4 and I had to use 0.18.3 instead. The node-gyp suggestion above did not solve this issue for me. Node v6.10.2, npm 3.10.10. |
I had same problem npm about binding -> https://www.npmjs.com/package/bindings |
this one worked for me |
Well, I tried the solutions above but none did work for me. So I solved it my way like this: module.exports = require('bindings')('xmljs'); to module.exports = require('bindings')({
"bindings": "xmljs",
"module_root": process.cwd() + "/node_modules/libxmljs",
}); Okay, it's not a bulletproof solution but it works for me. If anybody knows how to make this cleaner I want to hear it. |
After once you have done step as done by @MeiKatz go back to the root project folder i.e. |
What I did was copying as suggested by OP, and now it finally works.................. I wasted an afternoon. |
Hi, I tried installing libxmljs on a CentOS6.5 server and received the following error:
Everything seemed to build ok, and I tried rebuilding several times. (Sorry for the long paste):
So I investigated and tried copying
cp build/Release/lib.target/xmljs.node build/xmljs.node
from withinnode_modules/libxmljs/
and things started working. Not sure what the issue is with the bindings file not being copied to the proper location, but thought someone should know. Thanks.The text was updated successfully, but these errors were encountered: