env: bash\r: No such file or directory

Question

I'm trying to install YouCompleteMe from here.

When I execute:

./install.sh --clang-completer

I get this error:

env: bash\r: No such file or directory

I don't know what's wrong with environment variables. Here's my bash path:

which bash 
/bin/bash

Do I need to change it to /usr/bash? If yes, then how should I do that? I tried changing ~/.bashrc file, but it didn't work.

If your error was an error, it would probably contain the word "error". It is good that the "bash\r" file was not found because file names can't contain "\". — David Smolinski, Nov 23 '20 at 01:35
A quick fix :) just edit your script in notepad ++ editor and change the EOL conversion to UNIX(LF). I have also faced same issue after changing the EOL conversion to UNIX(LF) it is start working. — Aryashree Pritikrishna, Dec 23 '20 at 06:00

mklement0 · Accepted Answer · 2020-04-23T19:51:51.353

The error message suggests that the script you're invoking has embedded \r characters, which in turn suggests that it has Windows-style \r\n line endings instead of the \n-only line endings bash expects.

As a quick fix, you can remove the \r chars. as follows:

sed $'s/\r$//' ./install.sh > ./install.Unix.sh

^{Note: The $'...' string is an ANSI-C quoted string supported in bash, ksh, and zsh. It is used to ensure that the \r expands to an actual CR character before sed sees the script, because not all sed implementations themselves support \r as an escape sequence.}

and then run

./install.Unix.sh --clang-completer

However, the larger question is why you've ended up with \r\n-style files - most likely, other files are affected, too.

Perhaps you're running Git on Windows, where a typical configuration is to convert Unix-style \n-only line breaks to Windows-style \r\n line breaks on checking files out and re-converting to \n-only line breaks on committing.

While this makes sense for development on Windows, it gets in the way of installation scenarios like these.

To make Git check out files with Unix-style file endings on Windows - at least temporarily - use:

git config --global core.autocrlf false

Then run your installation commands involving git clone again.

To restore Git's behavior later, run git config --global core.autocrlf true.

score 36 · Answer 2 · answered Dec 27 '18 at 10:39

36

>vim gradlew
:set fileformat=unix
:wq
>./gradlew clean build

answered Dec 27 '18 at 10:39

Tuan Nguyen

2,151
15
25

score 18 · Answer 3 · edited Mar 14 '15 at 04:29

18

Your file has Windows line endings. Change to Unix line endings.

edited Mar 14 '15 at 04:29

mklement0

245,023
45
419
492

answered Mar 14 '15 at 03:41

Carl Norum

201,810
27
390
454

score 15 · Answer 4 · answered Feb 02 '17 at 18:08

15

Ran into something similar. You can use dos2unix install.sh to convert the line endings. Multiple files via find [pattern] | xargs dos2unix

answered Feb 02 '17 at 18:08

Michael Harris

150
1
4

3

You could use: `find . -type f -exec dos2unix {} \;` – s.ouchene Nov 27 '19 at 00:55

igonejack · Answer 5 · 2019-11-15T06:07:50.327

14

Quick command for converting line ending:

dos2unix thescript.sh

edited Nov 15 '19 at 06:07

answered Oct 05 '19 at 05:11

igonejack

1,580
15
25

score 14 · Answer 6 · answered Sep 16 '20 at 06:53

14

As the above comments say, it is happening due to windows line endings. To fix the issue follow these steps

For MAC:

brew install dos2unix # Installs dos2unix Mac
find . -type f -exec dos2unix {} \; # recursively removes windows related stuff

For Linux:

sudo apt-get install -y dos2unix # Installs dos2unix Linux
sudo find . -type f -exec dos2unix {} \; # recursively removes windows related stuff

And make sure your git config is set as follows:

git config --global core.autocrlf input

answered Sep 16 '20 at 06:53

salvi shahzad

542
5
16

1

Working Finally. I was facing this issue for 2 days and it was the isue of windows line endings from the project that I cloned from the github and finallly your solution was the perfect solution. thanks. – Riddhi Sep 17 '20 at 10:52
1

I am glad it helped you :) – salvi shahzad Sep 19 '20 at 15:26
1

yes, it woked. thanks @salvishahzad – Mohit Tomar Dec 15 '20 at 17:11
Thanks a lot. I had an issue when running a RN project. react-native run-android wasn't working. Tried all the possible scenarios to fix the issue. Finally this helps to fix that. – codehesh May 17 '21 at 12:59

luckyhandler · Answer 7 · 2020-06-16T07:52:07.940

In my case I had a wrong git configuration. The git documentation states:

If you’re programming on Windows and working with people who are not (or vice-versa), you’ll probably run into line-ending issues at some point

I'm using Mac OS and I exactly have this issue in one of my projects. To solve it I turned autocrlf to true which was wrong.

You can check the autocrlf state of your git configuration like this:

git config core.autocrlf

So if this returns true and the problem occurs within a git repository you'll have to change that configuration to

git config --global core.autocrlf input

on a Mac / Unix system. For Windows only projects you can use

git config --global core.autocrlf false

In my case I deleted the git repository and cloned it again and after that everything worked again as expected.

Find out more at https://www.git-scm.com/book/en/v2/Customizing-Git-Git-Configuration

you saved my day. I was struggling with this line ending issue for 2 days. — Tahmidur Rahman, Nov 15 '20 at 05:34

score 1 · Answer 8 · answered May 16 '20 at 22:09

In my case I had a wrong git configuration. The git documentation states:

If you’re programming on Windows and working with people who are not (or vice-versa), you’ll probably run into line-ending issues at some point

I'm using Mac OS and I exactly have this issue in one of my projects. To solve it I tuned autocrlf to true.

You can check the autocrlf state of your git configuration like this:

git config core.autocrlf

So if this returns true and the problem occurs within a git repository you'll have to change that configuration to

git config --global core.autocrlf input

which is the correct one for Mac / Unix systems. For Windows only projects you can use

git config --global core.autocrlf false

In my case I deleted the git repository and checked it out again and after that everything worked again as expected.

Find out more at https://www.git-scm.com/book/en/v2/Customizing-Git-Git-Configuration

You seem to have two identical answers on this question. – Roddy of the Frozen Peas Feb 19 '21 at 20:32 — Roddy of the Frozen Peas, Feb 19 '21 at 20:32

score 0 · Answer 9 · answered Jan 30 '21 at 18:48

In my case: This error occurs when I downloaded and unzip the WINDOWS version into MAC

and then added the windows version path to .bash_profile or .zprofile

so the solution for me was to remove the paths from (.bash_profile and .zprofile) then download the mac version by opening the terminal and type:

mkdir src
cd src
git clone https://github.com/flutter/flutter.git -b stable
export PATH="$PATH:pwd/flutter/bin"
flutter doctor

score -1 · Answer 10 · answered May 07 '20 at 08:38

-1

This link helped me solving the issue. https://github.com/tiangolo/uwsgi-nginx-flask-docker/issues/127

I edited my .sh file, replacing all CRLF with LF

answered May 07 '20 at 08:38

Raghav D

1
3

1

That's a very terrible thing to do. Please refer to the numerous better solutions provided above. – salvi shahzad Nov 17 '20 at 18:48

env: bash\r: No such file or directory

10 Answers10

Linked

Related