-bash: ./full_build.sh: /bin/bash^M: bad interpret
報錯信息：vim
執行一個腳本full_build.sh 時, 一直是提示我:bash
-bash: ./full_build.sh: /bin/bash^M: bad interpreter: No such file or directory編輯器
解決方案：ui
出現上面錯誤的緣由之一是腳本文件是DOS格式的, 即每一行的行尾以\r\n來標識, 使用vim編輯器打開腳本, 運行:spa
:set ff?unix
能夠看到DOS或UNIX的字樣. 使用set ff=unix把它強制爲unix格式的, 而後存盤退出, 便可.file
Name：Xr
im
Date：2014-05-31 22:55
腳本
相關文章
- 1. -bash: ./full_build.sh: /bin/bash^M: bad interpret
- 2. 解決/bin/bash^M: bad interpreter問題
- 3. Shell腳本報錯 /bin/bash^M: bad interpreter
- 4. /bin/bash^M: bad interpreter: No such file or dire
- 5. bash: ./vartest.sh: /bin/sh^M: bad interpreter: No
- 6. -bash: /etc/init.d/nginx: /bin/bash^M: bad interpreter: No such file or directory
- 7. 錯誤：-bash: ./how_paras.sh: /bin/bash^M: bad interpreter: No such file or directory
- 8. -bash: ./shellEq.sh: bin/bash: bad interpreter: 沒有那個文件或目錄
- 9. Bash腳本報錯：「/bin/bash^M: bad interpreter: No such file or directory」
- 10. -bash: ./backup.sh: /bin/bash^M: bad interpreter: No such file or directory
- 更多相關文章...
- • Docker exec 命令 - Docker命令大全
- • SOAP HTTP 協議 - SOAP 教程
- • Docker容器實戰(七) - 容器眼光下的文件系統
- • 使用阿里雲OSS+CDN部署前端頁面與加速靜態資源
相關標籤/搜索
每日一句
-
每一个你不满意的现在，都有一个你没有努力的曾经。
最新文章
歡迎關注本站公眾號,獲取更多信息
相關文章
- 1. -bash: ./full_build.sh: /bin/bash^M: bad interpret
- 2. 解決/bin/bash^M: bad interpreter問題
- 3. Shell腳本報錯 /bin/bash^M: bad interpreter
- 4. /bin/bash^M: bad interpreter: No such file or dire
- 5. bash: ./vartest.sh: /bin/sh^M: bad interpreter: No
- 6. -bash: /etc/init.d/nginx: /bin/bash^M: bad interpreter: No such file or directory
- 7. 錯誤：-bash: ./how_paras.sh: /bin/bash^M: bad interpreter: No such file or directory
- 8. -bash: ./shellEq.sh: bin/bash: bad interpreter: 沒有那個文件或目錄
- 9. Bash腳本報錯：「/bin/bash^M: bad interpreter: No such file or directory」
- 10. -bash: ./backup.sh: /bin/bash^M: bad interpreter: No such file or directory