12462 2018-01-02 20:42:19 +0000 Git configuration can break poky scripts 2018-02-22 15:23:53 +0000 1 1 7 Build System, Metadata & Runtime OE-Core Scripts and Tools 2.5 All Multiple RESOLVED NOTABUG Medium normal 2.5 M3 1 kratsg richard.purdie ross.burton --- --- Yes (doc changes required) oldest_to_newest 78869 0 kratsg 2018-01-02 20:42:19 +0000 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 78872 1 mhalstead 2018-01-02 22:39:12 +0000 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. 78896 2 ross.burton 2018-01-04 15:44:21 +0000 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? 79092 3 kratsg 2018-01-16 14:05:37 +0000 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. 79554 4 richard.purdie 2018-02-22 15:23:53 +0000 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.