Directory hard coded #2

dekz opened this Issue Feb 10, 2011 · 14 comments


None yet
9 participants

dekz commented Feb 10, 2011

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/", line 145, in prepare
prepare_impl(t, cwd, ver, wafdir)
File "/usr/local/bin/../lib/node/wafadmin/", line 135, in prepare_impl
File "/usr/local/bin/../lib/node/wafadmin/", line 188, in main
File "/usr/local/bin/../lib/node/wafadmin/", line 386, in build
return build_impl(bld)
File "/usr/local/bin/../lib/node/wafadmin/", line 405, in build_impl
File "/usr/local/bin/../lib/node/wafadmin/", line 268, in compile
OSError: [Errno 2] No such file or directory: '/home/lex/dev/projects/rbytes/build'

same problem.

Pull from github and npm install from inside that directory, fixed it for me

Same here, fails with
OSError: [Errno 2] No such file or directory: '/home/lex/dev/projects/rbytes/build'

ljantos commented Mar 31, 2011

same problem on Ubuntu here, but not on Mac OS

Same issue here, also on Ubuntu.

Since the source of rbytes doesn't contain any "home/lex" strings, I doubt that it is a rbytes issue.
I tried it on Ubuntu and Debian and both experience this problem .. on a Mac it works fine though. The NPM and node.js sources also don't contain any "home/lex" strings, so I would guess that it is most likely some problem with a library from Debian/Ubutnu (python?).

btw: tbranyen's workaround worked for me too

It's a strange issue. If installing from the git repo fixes it, then presumably it has nothing to do with the OS libraries, but I can't find any other explanation.

GitHub and NPM are not necessarily 1:1 its quite possible the author pushed broken code to NPM and working code to GitHub...

Package in NPM repo contains lines in \package\build\c4che\

LIBDIR = '/home/lex/.node_libraries'
NODE_PATH = '/home/lex/.node_libraries'

Maybe that's it.


akdubya commented Apr 21, 2011

Yeah NPM is doing some weird shit here w.r.t. propagating the local cache. I'll see what I can do about fixing the package.

I'm still getting this error when installing from npm due to /home/lex/dev/projects/rbytes/build being hard-coded inside. Unfortunately, I can't pull from github, because my hosting provider uses npm to resolve dependencies.

Will this be fixed soon?


akdubya commented May 9, 2011

I just forced a rebuild of the package and tested everything locally from another user. Let me know if this works for you.

tbranyen commented May 9, 2011

Seems fixed on my end.

On Mon, May 9, 2011 at 3:12 PM, akdubya <>wrote:

I just forced a rebuild of the package and tested everything locally from
another user. Let me know if this works for you.

Reply to this email directly or view it on GitHub:
#2 (comment)

It's fixed. Thanks, akdubya.

@akdubya akdubya closed this May 13, 2011

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