Windwos /usr/bin/env: ?bash?: No Such File Or Directory

Windows /usr/bin/env: bash : no such file or directory free

In my case, I had previously installed virtualenvwrapper using apt-get install virtualenvwrapper and later uninstalled it using apt-get remove virtualenvwrapper, which left the 'configuration' file /etc/bashcompletion.d/virtualenvwrapper behind. This bash completion definition was sourced by bash (it had nothing to do with my.bashrc) and caused the error message.The solution was to run: sudo apt-get purge virtualenvwrapperWhich purged all files related to virtualenvwrapper.

The reason I uninstalled it was to use pip's version instead (more up-to-date), which can be installed globally using: sudo pip install virtualenvwrapper. Following, I found that the error occurred when sourcing the virtualenvwrapper bash script, i.e.: source /usr/local/bin/virtualenvwrapper.shThe script references the file /etc/bashcompletion.d/virtualenvwrapper as pointed out by arcticfeather.Open up the script using the following command: sudo nano /etc/bashcompletion.d/virtualenvwrapperThis is where the non-existent file is being referenced. Simply replace /usr/share/virtualenvwrapper/virtualenvwrapperlazy.sh with /usr/local/bin/virtualenvwrapperlazy.sh and you should be good to go!

I installed a program on linux (UBUNTU), I set the environment variables.Unfortunately when I type the command to start the program it gave me theMessage: No such a file or directory.I can see the file, its permission is set to be executable. I can't seewhy?I installed this program on Mac and windows before and this never happened!:(Here is the link to the softwareHere is more info:it is XLE! :/Desktop$ xlebash: /home/yasaman/Desktop/XLE/bin/xle: No such file or directoryThis clearly shows that the file is on your PATH, and has execute permissions.The most frequent cause of ENOENT error under these conditions is a missing or corrupt dynamic loader. The not a dynamic executable error from ldd is another indication that that's what's happening.When a kernel execves a dynamic executable, it doesn't actually run the executable itself. Instead, it runs the dynamic loader, and the loader actually arranges for the executable to start, after mapping all required shared libraries.What does readelf -l xle say? Does the path specified in INTERP segment exist?

Is it executable?Since the file is a 32-bit ELF executable, are you perhaps on a 64-bit only system? If so, you'll need to install libc6-i386 package.

Posted on