Issue #2 open

Build failure on OS X 10.6

Anonymous created an issue

{{{

$ npm i uuid npm info it worked if it ends with ok npm info using npm@0.3.18 npm info using node@v0.4.7 npm info preinstall uuid@0.0.2 Checking for program g++ or c++ : /usr/bin/c++ /usr/lib/node/.npm/uuid/0.0.2/package/wscript:14: error: could not configure a cxx compiler! npm info uuid@0.0.2 Failed to exec preinstall script npm ERR! install failed Error: uuid@0.0.2 preinstall: node-waf configure && node-waf build npm ERR! install failed sh "-c" "node-waf configure && node-waf build" failed with 1 npm ERR! install failed at ChildProcess.<anonymous> (/usr/lib/node/.npm/npm/0.3.18/package/lib/utils/exec.js:49:20) npm ERR! install failed at ChildProcess.emit (events.js:67:17) npm ERR! install failed at ChildProcess.onexit (child_process.js:192:12) npm info install failed rollback npm info uninstall [ 'uuid@0.0.2' ] npm info preuninstall uuid@0.0.2 npm info uninstall uuid@0.0.2 npm info auto-deactive not symlink npm info postuninstall uuid@0.0.2 npm info uninstall uuid@0.0.2 complete npm info install failed rolled back npm ERR! Error: uuid@0.0.2 preinstall: node-waf configure && node-waf build npm ERR! sh "-c" "node-waf configure && node-waf build" failed with 1 npm ERR! at ChildProcess.<anonymous> (/usr/lib/node/.npm/npm/0.3.18/package/lib/utils/exec.js:49:20) npm ERR! at ChildProcess.emit (events.js:67:17) npm ERR! at ChildProcess.onexit (child_process.js:192:12) npm ERR! npm ERR! Failed at the uuid@0.0.2 preinstall script. npm ERR! This is most likely a problem with the uuid package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node-waf configure && node-waf build npm ERR! You can get their info via: npm ERR! npm owner ls uuid npm ERR! There is likely additional logging output above. npm ERR! System Darwin 10.7.0 npm ERR! argv { remain: [ 'uuid' ], npm ERR! argv cooked: [ 'i', 'uuid' ], npm ERR! argv original: [ 'i', 'uuid' ] } npm not ok

}}}

Comments (1)

  1. Nikhil Marathe repo owner
    • changed status to open

    Please check if your compiler works properly, because it builds perfectly on mine. Cloning the original repo and then running 'node-waf configure && node-waf' should give you more output. Note that this package has not been updated to work with the new npm and will not compile the C++ binding when installed via npm. So its best to do it manually.

  2. Log in to comment