/bin/sh^M: bad interpreter: No such file or directory

17
votes

When I enter brew doctor (or any brew command) in my terminal, I get this as a response:

-bash: /usr/local/bin/brew: /bin/sh^M: bad interpreter: No such file or directory

I have seen the ^M response before and I think it has to do with dos line ending files. Is there a way to fix this?

2
bashmacosterminalhomebrew
This happened to me, and I figured out why. I had copied my .gitconfig over from my windows machine, and didn't change the core.autocrlf to input before installing brew. D'oh! I think Javier Roca's solution is the nicest. – Kevin Pauli
Possible duplicate of ./configure : /bin/sh^M : bad interpreter – mklement0
Possible duplicate of Bash script: bad interpreter – jww

2 Answers

35
votes

I don't know how carriage returns ended up in your brew file, but you can remove them using dos2unix or by piping it through tr -d '\r'.

Example:

tr -d '\r'  < /usr/local/bin/brew   > myfixedbrew

Once verified, you can use

mv myfixedbrew /usr/local/bin/brew && chmod a+x /usr/local/bin/brew

to replace the old one.

35
votes

This worked for me:

  1. Open file /usr/local/bin/brew with vi (vi /usr/local/bin/brew)
  2. While on vi issue this commad (via esc or :) :set fileformat=unix
  3. Close file on vi via :wq!

The brew command should be OK now.

Regards.