FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

No suitable image found. · Issue #46 · nodegit/nodegit · GitHub

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

  1. fatlotus commented on Nov 28, 2012

    Contributor

    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?

  2. tgvashworth commented on Nov 29, 2012

    Author

    I am indeed, 10.8.2.

    I believe I first installed it with npm install gitteh, which I removed using npm rm, and then tried nodegit.

  3. tgvashworth commented on Nov 29, 2012

    Author

    I get this error when using npm install nodegit:

    warning: ignoring file /Users/tom/dev/leftlogic/gitdb/node_modules/nodegit/vendor/libgit2/build/libgit2.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /Users/tom/dev/leftlogic/gitdb/node_modules/nodegit/vendor/libgit2/build/libgit2.dylib
    
  4. faceleg commented on Feb 27, 2013

    Collaborator

    For now, please try:

    npm install git://github.com/tbranyen/nodegit.git

  5. tbranyen commented on Feb 27, 2013

    Member

    Bizarre, this is definitely an OS X issue. Works fine for me in Linux. Will investigate.

  6. faceleg commented on Feb 28, 2013

    Collaborator

    Hopefully bumping npm's version to 0.0.7 will fix this, I will push the 0.0.7 tag to npmjs.org tonight.

  7. tbranyen commented on Feb 28, 2013

    Member

    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.

  8. faceleg commented on Feb 28, 2013

    Collaborator

    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.

  9. faceleg commented on Feb 28, 2013

    Collaborator
  10. tbranyen commented on Mar 1, 2013

    Member

    This appears to be an architecture problem. Are you running a 32bit OS @faceleg? I think 64bit users are facing the problem.

  11. faceleg commented on Mar 2, 2013

    Collaborator

    @tbranyen no, I'm using Mountain Lion & Ubuntu 12.10 x64

  12. faceleg commented on Mar 21, 2013

    Collaborator

    Fixed in v0.0.74.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL