Skip to content

Issue with DOS/Unix line ending incompatibilities #31

Description

@Carson365

I'm having an issue trying to run this script from my Windows PC. I've tried running it through a VM and it just wasn't working (probably user error), and I've tried the Windows Subsystem for Linux and was running into this error: /bin/bash^M: bad interpreter: No such file or directory.

According to Google the problem is that the file endings confuse Unix, and following the commands "sed -i -e 's/\r$//'" and "sed -i -e 's/^M$//'" (per https://stackoverflow.com/questions/14219092/bash-script-and-bin-bashm-bad-interpreter-no-such-file-or-directory) solved it for Flash.sh, but the issue continues on farther down the line to ./Flash.sh: ./chip-update-firmware.sh and likely beyond. Is there anything you can do about this?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions