Closed ajshedivy closed 1 year ago
@ajshedivy I did a quick test cloning the main branch from GitHub into a directory on an IBM i sandbox - and no problems making and running sc...
I think you should check your git config - especially if you run git on windows sending files to IBM i using SSHFS: git on Windows will by default extract files using CRLF as line endings. Git on Mac/Linux/IBM i uses LF as line endings.
@ajshedivy Just a clarification - I used a SSH terminal into the IBMi sandbox and did the git clone in the terminal. So git was running on IBM i, not on Windows.
When doing cross-platform development or using SSHFS, be careful not to send Windows files into the Mac/Linux/IBM i box - as you discovered, they use different line ending codes than Windows. You can develop on Windows without problems - just keep the git repository on Windows and push to the remote and pull on the machine where the code is meant to be compiled / run.
You can control the line endings used by git - see the autocrlf config value.
We can close this issue for now since I think we understand the root cause.
If this is a persistent problem, I'm not opposed to putting some dos2unix
calls in the Makefile or something
Describe the bug While working on other issues, I noticed that after running
make install
that thesc
command does not work.To Reproduce
from the sc root directory, call
make install
then invoke the sc command.Expected behavior the sc usage message should be displayed (indicating that it is working)
Additional context I am using SSHFS-Win (windows) for remote development on sc. During my testing and editing It seeming some of the internal sc source files are being converted to windows line endings. If I use dos2unix on the sc script, things work as expected:
Is this something that needs to be investigated further?