-
Notifications
You must be signed in to change notification settings - Fork 302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
env: node\r: No such file or directory #75
Comments
I had this problem too on OSX. I just opened This should work on any OS because you'll be replacing the line break with what your OS expects. (Edited) |
Same problem here on Mac OS X. |
Same problem here on Mac OS X 10.9 |
@stevenvachon doesn't work for me |
Oops, I'd missed something. Edited original comment. |
I resolved this issue converting the line ending from DOS to UNIX format. |
@lp76 this works for me |
The project is missing a .gitattributes file. Since this is a public repository used by people, we can't (shoudn't) rewrite history, so it'll need to be added with a commit that changes all the line endings in most of the files. That would make it hard for current pull requests to be merged (so maybe it should wait), but afterwards it might avoid other problems with pull requests.. |
Same problem here on Mac OS X 10.9.4 |
@lp76 yeah that |
Same problem here on Mac OS X 10.9.5 and Travis CI. |
Same problem here on Mac OS X 10.10. |
@1j01 sure that'll fix it yeah? |
@adam-lynch Simply adding the .gitattributes file won't (necessarily) normalize the line-endings in existing files. It's governed by cryptic voodoo. There usually needs to be a commit that changes all the line endings in most of the files. It probably depends on what line-endings happen to be in the files currently. |
@1j01 I've done it before (from https://help.github.com/articles/dealing-with-line-endings/) but just asking if you're sure this is because of line-endings. I can look into normalizing them soon |
command |
@adam-lynch I don't know. People have apparently been fixing it by changing line endings, so I figure that's the issue. I haven't experienced the issue myself, but it makes sense. |
@stevenvachon This works for me :) |
Closing in favour of #105 |
+1 for this. Have the same issue. Can't build my node-webkit anymore from osx 10.10.1. |
By the way, for anyone having this issue, you might have to fix the file You can do this:
tofrodos will convert \r to \n and back (fromdos/todos). |
before the actual fix, one can use following command:
|
When I run |
Can't run nwbuild
It returns env: node\r: No such file or directory with every execution
nwbuild -r .
env: node\r: No such file or directory
nwbuild -h
env: node\r: No such file or directory
The text was updated successfully, but these errors were encountered: