When cloning poky with the git config set "core.autocrlf=true", sourcing the scaffolding script breaks: $ source oe-init-build-env : command not found : command not found -bash: oe-init-build-env: line 30: syntax error near unexpected token `elif' 'bash: oe-init-build-env: line 30: `elif [ -n "$ZSH_NAME" ]; then To reproduce: git config core.autocrlf true git clone -b pyro git://git.yoctoproject.org/poky cd poky source oe-init-build-env
We can't control this on the infrastructure side as far as I know. The end user can control this setting or the repository owner can add a .gitattributes file and set "text eol=lf". I'm moving this to where the repository owners will see it.
Context: core.autocrlf=true tells git to force every text file to use Windows line endings, but on Linux shell scripts needs Linux line endings. Why do you have autocrlf=true set?
Hi, sorry for late response. This was needed between we're running Vivado/SDK on Windows machines and yocto/bitbake on Linux machines -- and having to run version control on both.
You can't clone linux based shell scripts with that setting and expect them to work and this isn't something we can fix, sorry.