Skip to content

Instantly share code, notes, and snippets.

@erichocean

erichocean/gist:5177582

Created March 16, 2013 18:10
Show Gist options
  • Save erichocean/5177582 to your computer and use it in GitHub Desktop.
Save erichocean/5177582 to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. erichocean created this gist Mar 16, 2013.
    37 changes: 37 additions & 0 deletions gistfile1.txt
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,37 @@
    Here's the error I was getting:

    mila:node-sqlite3 onitunes$ ./configure
    gyp info it worked if it ends with ok
    gyp info using [email protected]
    gyp info using [email protected] | darwin | x64
    gyp ERR! configure error
    gyp ERR! stack Error: Command failed: execvp(): No such file or directory
    gyp ERR! stack
    gyp ERR! stack at ChildProcess.exithandler (child_process.js:540:15)
    gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:99:17)
    gyp ERR! stack at maybeClose (child_process.js:638:16)
    gyp ERR! stack at Socket.ChildProcess.spawn.stdin (child_process.js:815:11)
    gyp ERR! stack at Socket.EventEmitter.emit (events.js:96:17)
    gyp ERR! stack at Socket._destroy.destroyed (net.js:358:10)
    gyp ERR! stack at process.startup.processNextTick.process._tickCallback (node.js:244:9)
    gyp ERR! System Darwin 11.4.2
    gyp ERR! command "node" "/usr/local/bin/node-gyp" "configure"
    gyp ERR! cwd /Users/onitunes/Dropbox/code/fohr-caprica/node_modules/node-sqlite3
    gyp ERR! node -v v0.8.17
    gyp ERR! node-gyp -v v0.9.1
    gyp ERR! not ok

    The problem was that my `$PYTHON` was pointing to MacPorts, which I had uninstalled:

    mila:fohr-dataset onitunes$ echo $PYTHON
    /opt/local/bin/python

    First, I set it back to what it should be:

    export PYTHON=/usr/bin/python

    Then I went and fixed my ~/.profile (remove this line, it's probably at the end):

    export PYTHON=/opt/local/bin/python

    You should be good to go. Thanks to `niggler` on the #node.js channel for help.