Usr/local/bin/virtualenvwrapper.sh No Such File Or Directory

Posted on by admin

What do you mean by manually?-- if you put the variables in the bashrc file, it should always work. – x - y Nov 17 '12 at 16:11 1 What I mean is that there's no reason to define these variables outside of virtualenvwrapper.sh unless you have a good reason to.

This repository has been archived by the owner. It is now read-only.

Join GitHub today

GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.

Sign up

Comments

Stdio.h No Such File Or Directory

File

commented Aug 23, 2012

This happens in version 0.6.x on ubuntu. Does not happen above 0.7.x

Member

commented Aug 23, 2012

Not a node bug. The node binary is not on your $PATH.

commented Sep 27, 2012

I've found this is often a misnaming error, if you install from a package manager you bin may be called nodejs so you just need to symlink it like so 'ln -s /usr/bin/nodejs /usr/bin/node'

commented Jan 17, 2013

digitalmediums,
That was useful, thanks a lot!

commented Jan 28, 2013

After 3 hours of suffering, this is the solution. Thank you digitalmediums. Why is this now misnaming happening now out of the blue?

commented Jan 28, 2013

@houmie (and everyone who comes across this bug in the future)

These explain why:

http://lists.debian.org/debian-devel-announce/2012/07/msg00002.html
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614907
http://debian.2.n7.nabble.com/Node-js-and-it-s-future-in-debian-td1042211.html (only read this last thread if you're a masochist)

As a Node developer, I would think hard before using Debian's packaged version of node, and would use Ubuntu with chrislea's PPA for Node or Debian stable with Node built from source in preference to the stock Debian nodejs package for the foreseeable future. The discussion on this bug makes clear that Debian has a very different idea of the role of Node in the wider world than most of the Node community.

commented Jan 29, 2013

@othiym23 Thank you for the explanation. :) I see there is a proper flame war around this. But its understandable when namespaces are broken. Hope they can resolve it at one stage.

commented Mar 5, 2013

@digitalmediums Thx

commented Mar 6, 2013

Thanks for the help.

commented Mar 15, 2013

@digitalmediums Thanks!

commented Apr 12, 2013

I installed via sudo make install.

npm still fails:

/work/qpp$ sudo npm install -g grunt-cli
/usr/bin/env: node: No such file or directory
/work/qpp$ node -v
v0.10.4
/work/qpp$ which node
/usr/local/bin/node

Member

commented Apr 12, 2013

@johnjbarton Try sudo PATH='$PATH:/usr/local/bin' npm install -g grunt-cli

commented Apr 12, 2013

Thanks. However in the meantime I uninstalled node, unintalled npm, then
installed node and installed npm. Then I was able to install grunt-cli.

On Fri, Apr 12, 2013 at 2:13 PM, Ben Noordhuis notifications@github.comwrote:

@johnjbartonhttps://github.com/johnjbarton Try sudo
PATH='$PATH:/usr/local/bin' npm install -g grunt-cli


Reply to this email directly or view it on GitHubhttps://github.com//issues/3911#issuecomment-16317844
.

commented Jun 5, 2013

Just do

$ sudo apt-get install nodejs-legacy

commented Jun 8, 2013

Yes, installing nodejs-legacy is the cleanest solution.

Imho trying to name a server with a generic word like node is pretty stupid and it is quite understandable that there is so much resistance in accepting such a name. Rename it back to something unique that is easy to google for and can not be mistaken for something else, like nodejs, and everyone will be happy.

Member

commented Jun 8, 2013

For very restricted definitions of 'everyone'. You're only two or three years late - that ship has long sailed.

commented Jun 8, 2013

That ship sailed a long time ago and those arguments only really apply to something that's not vastly popular. node.js is popular enough to claim the node name and expect other less popular programs not to conflict with it.

As for not being googlable: https://www.google.com/?q=node

commented Sep 3, 2013

Thanks,

referenced this issue Oct 20, 2013

Closed

OSX 10.8.5 node no such file or directory on bower list --json #44

commented Dec 2, 2013

@othiym23 : Thanks for the details on ubuntu/debian...

commented Dec 3, 2013

I had to append /usr/bin to PATH in my PHP code :

putenv('PATH=' . getenv('PATH') . ':/usr/local/bin:/usr/bin');

./configure: No Such File Or Directory

referenced this issue Dec 13, 2013

Closed

CommandException: Something went wrong while executing the command '/usr/bin/bower' 'install' env: node: No such file or directory #68

referenced this issue Dec 15, 2013

Open

Work for Ubuntu #4

commented Dec 23, 2013

'update-alternatives --install /usr/bin/node node /usr/bin/nodejs 99'

this fixed it for me

commented Dec 24, 2013

or just apt-get install nodejs-legacy

commented Jan 5, 2014

Error /usr/local/bin/virtualenvwrapper.sh no such file or directory

rlidwka's solution is the one, I arrived. Except the fact, I didn't see it & gone through infinite suffering.

commented Jan 5, 2014

rlidwka's solution is the one, I arrived. Except the fact, I didn't see it & gone through infinite suffering.

you sound like Zathras :)

referenced this issue Mar 7, 2014

Open

Check for /usr/bin/nodejs for Debian/Ubuntu based systems #92

commented Mar 14, 2014

i did :$ ln -s /usr/bin/nodejs /usr/bin/node

commented Mar 22, 2014

sudo ln -fs /usr/bin/nodejs /usr/local/bin/node

commented Oct 20, 2015

digitalmediums,
That was useful, thanks a lot!

commented Oct 25, 2015

Thank you, it worked for me!

referenced this issue Nov 13, 2015

Closed

node is missing #1

commented Nov 17, 2015

@digitalmediums you are right till now. thank you!
'if you install from a package manager you bin may be called nodejs so you just need to symlink it like so 'ln -s /usr/bin/nodejs /usr/bin/node'

commented Nov 29, 2015

Great!, thanks for the post

commented Dec 1, 2015

Symlink worked great for Debian deploy, thanks!

referenced this issue Dec 14, 2015

Closed

[Installation] Install Command-Line Tool doesn't work for me #7507

commented Dec 18, 2015

sudo apt-get install nodejs-legacy
worked :) 👍

commented Jan 21, 2016

sudo apt-get install nodejs-legacy worked :)

commented Jan 26, 2016

Some Linux distributions installs NodeJS as nodejs and not node. Simply create a link as
ln -s /usr/bin/nodejs /usr/bin/node

commented Jan 27, 2016

thanks, my npm is working now.

commented Jan 28, 2016

@fgesora 's solution works for me, thanks 👍 (I use nvm)

commented Jan 28, 2016

Thanks, worked for me =)

referenced this issue Feb 22, 2016

Closed

/usr/bin/env: node: No such file or directory #9

referenced this issue Mar 5, 2016

Closed

Redux CLI exits with error #39

referenced this issue Mar 10, 2016

Closed

Tests are failing #202

commented Mar 11, 2016

Thanks @digitalmediums

commented Mar 17, 2016

thanks @digitalmediums

referenced this issue Mar 23, 2016

Closed

[Install Error] Error with 'gulp install' #2650

commented Apr 14, 2016

thanks @digitalmediums

referenced this issue Apr 16, 2016

Open

/usr/bin/env: node: No such file or directory #2

commented Apr 21, 2016

dude, thanks! @digitalmediums

commented Apr 21, 2016

@digitalmediums you are the great guy! This shitty issue still happens almost 4 yeah later.. (:

commented Apr 26, 2016

thanks for the help

referenced this issue Apr 28, 2016

Closed

azure cli in ubuntu, '/usr/bin/env: 'node': No such file or directory' #2830

commented May 4, 2016

I expected them to fix it after 3 years....

commented May 5, 2016

Wow, this issue has been since last 4 years... well thats interesting

commented May 11, 2016

Error 2 No Such File Or Directory

I found this amazing and shocking. Really lack of caring.

Member

commented May 11, 2016

For people coming here through search engines, the correct solution is #3911 (comment) or #3911 (comment).

To the last three commenters: If you are unhappy that Debian decided to call the binary nodejs instead of node, complain to Debian. Griping about it here won't help.

Locking.

locked and limited conversation to collaborators May 11, 2016

Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.