Wrong path for node-waf

[Qard]

I'm having issues installing topcube from npm. It looks like the package is broken. It tries to run node-waf in "/home/tim/Code/topcube/build". Here's the output;

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 fetch http://registry.npmjs.org/topcube/-/topcube-0.0.6.tgz
npm info calculating sha1 /tmp/npm-1304553693624/1304553693624-0.9122465958353132/tmp.tgz
npm info shasum 6271b42ab32c5074a6c28da2707c63bfec5b4817
npm info calculating sha1 /usr/local/lib/node/.npm/.cache/topcube/0.0.6/package.tgz
npm info shasum ba2647af3d080e4861caca2d6f19cf1c03320029
npm info preinstall topcube@0.0.6
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 gtk+-2.0                    : not found 
Checking for glib-2.0                    : yes 
Checking for webkit-1.0                  : not found 
'configure' finished successfully (0.765s)
Waf: Entering directory `/home/tim/Code/topcube/build'
Waf: Leaving directory `/home/tim/Code/topcube/build'
Traceback (most recent call last):
  File "/usr/local/bin/node-waf", line 16, in <module>
     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/tim/Code/topcube/build'
npm info topcube@0.0.6 Failed to exec preinstall script
npm ERR! install failed Error: topcube@0.0.6 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.<anonymous> (/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 [ 'topcube@0.0.6' ]
npm info preuninstall topcube@0.0.6
npm info uninstall topcube@0.0.6
npm info auto-deactive not symlink
npm info postuninstall topcube@0.0.6
npm info uninstall topcube@0.0.6 complete
npm info install failed rolled back
npm ERR! Error: topcube@0.0.6 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.<anonymous> (/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 topcube@0.0.6 preinstall script.
npm ERR! This is most likely a problem with the topcube 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 topcube
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 2.6.38-8-generic
npm ERR! argv { remain: [ 'topcube' ],
npm ERR! argv   cooked: [ 'install', 'topcube' ],
npm ERR! argv   original: [ 'install', 'topcube' ] }
npm not ok

[creationix]

Strange. There is nothing with hard-coded paths anywhere in the git repo. npm must have grabbed some waf cache file when publishing the package. You can try installing from source while I work on my end to see why it's acting weird.

[Qard]

I got it to compile manually. Too bad the libwebkitgtk-dev package on Ubuntu doesn't have WebGL support yet. :(

Any possibility of support for fullscreen switching and setting the tiltlebar text to match the <title /> element at some point in the future?

[ABHIJEET-MUNESHWAR]

I have node v0.4.11 & npm v1.0.27. Now I execute following command : npm install pcap Then I get following output: likewin@manju-desktop:~$ npm install pcap

pcap@0.2.8 install /home/likewin/node_modules/pcap node-waf configure clean build

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 Checking for library pcap : yes 'configure' finished successfully (0.079s) 'clean' finished successfully (0.006s) Waf: Entering directory /home/likewin/node_modules/pcap/build' [1/2] cxx: pcap_binding.cc -> build/default/pcap_binding_1.o [2/2] cxx_link: build/default/pcap_binding_1.o -> build/default/pcap_binding.node Waf: Leaving directory/home/likewin/node_modules/pcap/build' 'build' finished successfully (0.329s) pcap@0.2.8 ./node_modules/pcap

Can you please help me in solving the problem of "Checking for node path : not found" ? Thank you very much in advance

[creationix]

I don't know what "node path" is, but I don't think it's an error to be missing. It's normal for program configures to be missing some things in some valid configurations.

[ABHIJEET-MUNESHWAR]

I'm feeling happy to say that I could solve the below problem: "Checking for node path : not found" by setting the value for the variable NODE_PATH in terminal as follows: export NODE_PATH="/usr/local/lib/node"

[jaydeepw]

then why dont you clone the repo, fix the problem and submit a pull request.