[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Sat, 29 May 2021 02:21:14 -0600
From: Hustle Sec <hustlesec.info@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: Cygwin Compiling Error on Windows 10
Hello all,
I read through everything you all linked to and I was able to get it to
work by running:
git config --global auto.crlf false
This command must be ran before the git clone. After the clone is complete,
"auto.crlf" can be reset to "true", even before compiling, for anyone
concerned about changing global git settings.
I tried using "--local" in the above command to modify the local
.gitattributes file, but that didn't work. Also, I tried manually modifying
the local .gitattributes file using arguments from some of the provided
links and google, but I was unable to achieve success with that method.
Admittedly, a lot of that information was pretty over my head.
Big thank you to everyone that chimed in to help me solve this problem!
- HustleSec
On Thu, May 27, 2021, 8:28 AM Solar Designer <solar@...nwall.com> wrote:
> Hi,
>
> On Wed, May 26, 2021 at 12:36:48PM -0600, Hustle Sec wrote:
> > When attempting to run ./configure on /john/src in Cygwin on Windows 10 I
> > get the following error:
> >
> > $ ./configure
> > ./configure: line 16: $'\r': command not found
> > ./configure: line 31: syntax error near unexpected token newline'
> > '/configure: line 31: ;;
> >
> > Then the process quits. Is there anything I can do to fix this?
>
> Others have already provided some replies, but FWIW searching for
> mentions of related problems seen by other projects finds e.g.:
>
> https://github.com/reconquest/import.bash/issues/2
> https://community.perforce.com/s/article/2973
>
> Reading and summarizing these and the like, it appears that:
>
> Git on Windows defaults to using CRLF for text files ("On windows
> systems core.autocrlf is normally set to "true" globally.")
>
> To avoid the problem, one can "do a "git -c core.autocrlf=input clone
> ..." and finally set core.autocrlf=input locally".
>
> As a workaround, it can be possible to "make use of "set -o igncr"
> (warning: cygwin bash only!)". It may also be required to "export
> SHELLOPTS" for this to work.
>
> As another workaround, the project could "add .gitattributes file [...]
> and force git to handle shell scripts eol=lf". Maybe we should?
>
> Alexander
>
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
