You can’t build the sources if you haven’t fully checked them out yet, and you haven’t fully checked them out yet if you didn’t run the git submodule update command. What error do you get when you run git submodule update --init --recursive? Did you remember to cd into the freedom-e-sdk dir first?
Odd. The only case I can think of where git submodule does nothing is if you already ran it and it already worked. What do you see if you run “ls freedom-metal”? If you see an empty dir, then the submodule has not been updated yet. If you see files in there, then the configure file should be one of them. You should also try “git status” in case maybe the initial clone of freedom-e-sdk had a problem. And you should try “git branch” to see what branch you are on. You should be on the default v201908-branch branch.
The error is
/bin/sh: 2: /home/kanika812/Desktop/freedom-e-sdk/freedom-metal/configure: not found
if that file exists, then that suggests that /bin/sh is broken. Or maybe the configure script is corrected.
What does “ls -lt /bin/sh” say? What happens if you try to run that configure script by hand?
I meant “configure corrupted” not “configure corrected”. The error message suggests a windows/linux incompatibility. Windows uses ^M^J to end a line, linux uses ^J to end a line. If you have a windows version of the file that is using ^M^J as a line ending, and run that on a linux shell, you will get that error. I can reproduce by manually editing my copy of the file to look like a windows file. So now the question is how did you manage to get a windows file on a linux system?
There is a git config feature where you can specify line endings. If you have core.eol set to crlf in your ~/.gitconfig file that could cause this problem. Or maybe you are on a window system, and using the linux subsystem, or cygwin, or something?