You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running build.sh, I get an error bash: ./build.sh: /bin/sh^M: bad interpreter: No such file or directory.
This is not to do with path configuration as far as I can tell; perhaps something odd with the encoding of the file? I have very limited Docker / WSL experience.
Making a new executable file in the same location with the same text content seems to work fine (although I did need to do a git submodule sync --recursive as well, which should perhaps be mentioned in readme or included in script).
The text was updated successfully, but these errors were encountered:
I ended up copying the contents of build.sh into another file with a different name and then it mysteriously worked. Never did get to the bottom of that.
Also reviewing my notes I see that I missed a git submodule sync --recursive at one point. That got me a working build (although I also changed .gitmodules where it refers to url = ../../chafey/openjpeg.git to have an absolute path, but I don't think that was necessary to make the build work).
Side-note: I also changed a bit of the configuration to gobble a bit less memory and not spam the log, and have been quite happily running a little pool of workers.
When running build.sh, I get an error
bash: ./build.sh: /bin/sh^M: bad interpreter: No such file or directory
.This is not to do with path configuration as far as I can tell; perhaps something odd with the encoding of the file? I have very limited Docker / WSL experience.
Making a new executable file in the same location with the same text content seems to work fine (although I did need to do a
git submodule sync --recursive
as well, which should perhaps be mentioned in readme or included in script).The text was updated successfully, but these errors were encountered: