New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unix_setup.sh script error due to ^M #5153
Comments
Running |
I get the "bad interpreter" error as well when running with "./unix_setup.sh". When I run "sh unix_setup.sh" I get some really nonsensical output:
|
Update: running dos2unix on the setup script resolves these issues for me as well. |
Are you guys running this from the "ZIP" file or from source code? If ZIP, we should fix this in the installer. |
I also used the ZIP file. |
I too got this issue from the zip and fixed it in the same way. It does seem to be an issue with the installer. |
We are addressing this - for the next release, the script will have the
correct line endings.
…On Sun, Oct 6, 2019 at 4:04 PM Ryan Kozak ***@***.***> wrote:
Are you guys running this from the "ZIP" file or from source code?
If ZIP, we should fix this in the installer.
I too got this issue from the zip and fixed it in the same way. It does
seem to be an issue with the installer.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#5153?email_source=notifications&email_token=AANCLRN7SUNKOWSABI3Q2K3QNJAD7A5CNFSM4ITSWSXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAOSXRY#issuecomment-538782663>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AANCLRJGHIG4ZNMAA4VDMO3QNJAD7ANCNFSM4ITSWSXA>
.
|
this is easy to fix:
done. |
When I run the unix_setup.sh script I get this error:
./unix_setup.sh: /bin/bash^M: bad interpreter: No such file or directory
This error happens because the file was saved with "windows style" end of the line (\r\n), which appears as ^M at the end of every line:
cat -Te unix_setup.sh
This error can be easily fixed:
dos2unix unix_setup.sh
The text was updated successfully, but these errors were encountered: