Repository navigation
No suitable image found. #46
Description
I'm seeing the following error when I require('nodegit'):
Error: dlopen(/Users/tom/.node_modules/nodegit/build/Release/nodegit.node, 1): no suitable image found. Did find:
/Users/tom/.node_modules/nodegit/build/Release/nodegit.node: mach-o, but wrong architecture
I've get the same if I npm install nodegit or build from source.
FWIW it's work I also get this using the other libgit2 node library, gitteh.
Activity
fatlotus commentedon Nov 28, 2012
I take it you're using Mac OS X on Intel, yes? What version are you using?
Also, have you installed libgit2 before? If so, what method did you use to install it?
tgvashworth commentedon Nov 29, 2012
I am indeed, 10.8.2.
I believe I first installed it with
npm install gitteh, which I removed usingnpm rm, and then tried nodegit.tgvashworth commentedon Nov 29, 2012
I get this error when using
npm install nodegit:faceleg commentedon Feb 27, 2013
For now, please try:
npm install git://github.com/tbranyen/nodegit.gittbranyen commentedon Feb 27, 2013
Bizarre, this is definitely an OS X issue. Works fine for me in Linux. Will investigate.
faceleg commentedon Feb 28, 2013
Hopefully bumping
npm's version to 0.0.7 will fix this, I will push the 0.0.7 tag to npmjs.org tonight.tbranyen commentedon Feb 28, 2013
Unsure, I installed from git and still received the same error. Might be an issue with wscript and node-waf?
Would be great if we could switch over to node-gyp.
faceleg commentedon Feb 28, 2013
Yes I was planning on moving to
node-gyp, among other things.I'm intending to make a roadmap wiki page tonight, so we can make sure nobody works over the top of anyone else.
faceleg commentedon Feb 28, 2013
@tbranyen it's here: https://github.com/tbranyen/nodegit/wiki/Road-map
tbranyen commentedon Mar 1, 2013
This appears to be an architecture problem. Are you running a 32bit OS @faceleg? I think 64bit users are facing the problem.
faceleg commentedon Mar 2, 2013
@tbranyen no, I'm using Mountain Lion & Ubuntu 12.10 x64
faceleg commentedon Mar 21, 2013
Fixed in v0.0.74.