Ticket #7673 (closed bug: fixed)
Windows: run "git config --global core.autocrlf false" before cloning the repo
Description
On my windows box, I experienced the following loop:
GROOB:~/work $ git clone git@github.com:ghc/ghc.git Cloning into 'ghc'... remote: Counting objects: 223976, done. remote: Compressing objects: 100% (44932/44932), done. remote: Total 223976 (delta 179757), reused 222061 (delta 178061) Receiving objects: 100% (223976/223976), 67.25 MiB | 560 KiB/s, done. Resolving deltas: 100% (179757/179757), done. GROOB:~/work $ cd ghc GROOB:~/work/ghc $ ls ANNOUNCE SUBMAKEHELP config.sub* ghc.mk mk/ tarballs HACKING aclocal.m4 configure.ac ghc.spec.in packages utils/ LICENSE bindisttest/ distrib/ includes/ rts/ validate* MAKEHELP boot* docs/ install-sh* rules/ Makefile compiler/ driver/ libffi/ settings.in README config.guess* ghc/ libraries/ sync-all* GROOB:~/work/ghc $ ./sync-all get at ./sync-all line 287. == Checking for old haddock repo == Checking for old binary repo == Checking for old mtl repo == Checking for old Cabal repo == Checking for old time from tarball ============================ ATTENTION! You have an old time package in your GHC tree! Please remove it (e.g. "rm -r libraries/time"), and then run "./sync-all get" to get the new repository. ============================ GROOB:~/work/ghc $ l libraries/time ./ ../ GROOB:~/work/ghc $ rm -rf libraries/time GROOB:~/work/ghc $ l libraries/time /bin/ls: libraries/time: No such file or directory GROOB:~/work/ghc $ ./sync-all get at ./sync-all line 287. == Checking for old haddock repo == Checking for old binary repo == Checking for old mtl repo == Checking for old Cabal repo == Checking for old time from tarball ============================ ATTENTION! You have an old time package in your GHC tree! Please remove it (e.g. "rm -r libraries/time"), and then run "./sync-all get" to get the new repository. ============================ GROOB:~/work/ghc $
Turns out the problem is solved by deleting the repo, running:
git config --global core.autocrlf false
and checking out the repo again.
Attachments
Change History
Note: See
TracTickets for help on using
tickets.

