japj / node-sdlmixer

sdlmixer addon for nodejs

Home Page:http://github.com/japj/node-sdlmixer

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Path based dependencies.

ncb000gt opened this issue · comments

It looks like your home directory is stashed somewhere in your files. And, those files got pushed to npm. If I do spend more time on it I'll send a pull request. Otherwise, here's your ticket. :)

sudo npm install node-sdlmixer
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 node-sdlmixer@0.0.1
Nothing to clean (project not configured)
Checking for program g++ or c++ : /usr/bin/g++
Checking for program cpp : /usr/bin/cpp
Checking for program ar : /usr/bin/ar
Checking for program ranlib : /usr/bin/ranlib
Checking for g++ : ok
Checking for node path : not found
Checking for node prefix : ok /usr/local
Checking for program sdl-config : /usr/bin/sdl-config
'configure' finished successfully (0.037s)
Waf: Entering directory /home/japj/github/node-sdlmixer/build' Waf: Leaving directory/home/japj/github/node-sdlmixer/build'
Traceback (most recent call last):
File "/usr/local/bin/node-waf", line 16, in
Scripting.prepare(t, os.getcwd(), VERSION, wafdir)
File "/usr/local/bin/../lib/node/wafadmin/Scripting.py", line 145, in prepare
prepare_impl(t, cwd, ver, wafdir)
File "/usr/local/bin/../lib/node/wafadmin/Scripting.py", line 135, in prepare_impl
main()
File "/usr/local/bin/../lib/node/wafadmin/Scripting.py", line 188, in main
fun(ctx)
File "/usr/local/bin/../lib/node/wafadmin/Scripting.py", line 386, in build
return build_impl(bld)
File "/usr/local/bin/../lib/node/wafadmin/Scripting.py", line 405, in build_impl
bld.compile()
File "/usr/local/bin/../lib/node/wafadmin/Build.py", line 268, in compile
os.chdir(self.bldnode.abspath())
OSError: [Errno 2] No such file or directory: '/home/japj/github/node-sdlmixer/build'
npm info node-sdlmixer@0.0.1 Failed to exec preinstall script
npm ERR! install failed Error: node-sdlmixer@0.0.1 preinstall: node-waf clean || true; node-waf configure build
npm ERR! install failed sh "-c" "node-waf clean || true; node-waf configure build" failed with 1
npm ERR! install failed at ChildProcess. (/usr/local/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 [ 'node-sdlmixer@0.0.1' ]
npm info preuninstall node-sdlmixer@0.0.1
npm info uninstall node-sdlmixer@0.0.1
npm info auto-deactive not symlink
npm info postuninstall node-sdlmixer@0.0.1
npm info uninstall node-sdlmixer@0.0.1 complete
npm info install failed rolled back
npm ERR! Error: node-sdlmixer@0.0.1 preinstall: node-waf clean || true; node-waf configure build
npm ERR! sh "-c" "node-waf clean || true; node-waf configure build" failed with 1
npm ERR! at ChildProcess. (/usr/local/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 node-sdlmixer@0.0.1 preinstall script.
npm ERR! This is most likely a problem with the node-sdlmixer package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-waf clean || true; node-waf configure build
npm ERR! You can get their info via:
npm ERR! npm owner ls node-sdlmixer
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 2.6.38-8-generic
npm ERR! argv { remain: [ 'node-sdlmixer' ],
npm ERR! argv cooked: [ 'install', 'node-sdlmixer' ],
npm ERR! argv original: [ 'install', 'node-sdlmixer' ] }
npm not ok

Apparently something in my .gitignore directory got bundled up in the npm publish. I upgraded to the latest npm and did some small documentation updates, cleaned up my build directory and pushed version 0.0.2.

Let me know if it still doesn't work for you

Yea. It happens. I've had it happen with a few of my modules. :)

I'll check again later.

closing this issue, if you still have an issue feel free to submit/reopen