git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git Cygwin - unable to create any repository - help!

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 16, 2008, 17:55 UTC
Message-ID
<7v1w8hslhw.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<a5eb9c330801160742j645ee50p72ee0a93adf8f94f@mail.gmail.com>
"Paul Umbers" <paul.umbers@gmail.com> writes:
Show 13 quoted lines
> OK, I think this worked (I'm a Java man, not C/C++). I downloaded the
> latest 1.5.3 source from the git repository and ran "make" with
> GIT_TEST_OPTS="--verbose --debug". Here's the output:
>
> paulumbers@Devteam29 ~/workspace/git/git-1.5.3/t
> $ make
> *** t0000-basic.sh ***
> *   ok 1: .git/objects should be empty after git init in an empty repo.
> *   ok 2: .git/objects should have 3 subdirectories.
> *   ok 3: git update-index without --add should fail adding.
> *   ok 4: git update-index with --add should succeed.
> * FAIL 5: writing tree out with git write-tree
>         tree=$(git write-tree)

Often the first error is the most interesting, as your build is failing the most basic operation (like creating a tree), and later parts of the test uses the tree to validate other aspects of your build.

After seeing the above error, running the test with -i (stop immediately on failure):

	$ cd t
        $ sh -x ./t0000-basic.sh -i -v

and looking at the exact command that fails is the usual approach for debugging something like this. During that debugging session, the contents of the directory t/trash (which is where the test script runs) left by the failed test is what we often do.

Previous: Paul UmbersNext: Paul Umbers
Message 16 of 39 in “Git Cygwin - unable to create any repository - help!”
  1. Paul UmbersJan 14, 2008
  2. Alex RiesenJan 14, 2008
  3. Paul UmbersJan 14, 2008
  4. Alex RiesenJan 15, 2008
  5. Paul UmbersJan 15, 2008
  6. Alex RiesenJan 15, 2008
  7. Paul UmbersJan 15, 2008
  8. Alex RiesenJan 15, 2008
  9. Paul UmbersJan 15, 2008
  10. Alex RiesenJan 15, 2008
  11. Paul UmbersJan 15, 2008
  12. Alex RiesenJan 15, 2008
  13. Robin RosenbergJan 15, 2008
  14. Alex RiesenJan 16, 2008
  15. Paul UmbersJan 16, 2008
  16. Junio C HamanoJan 16, 2008
  17. Paul UmbersJan 16, 2008
  18. Alex RiesenJan 16, 2008
  19. Paul UmbersJan 16, 2008
  20. Alex RiesenJan 16, 2008
  21. Paul UmbersJan 16, 2008
  22. Alex RiesenJan 16, 2008
  23. Alex RiesenJan 16, 2008
  24. Paul UmbersJan 16, 2008
  25. Alex RiesenJan 16, 2008
  26. Paul UmbersJan 17, 2008
  27. Linus TorvaldsJan 17, 2008
  28. Johannes SchindelinJan 17, 2008
  29. Paul UmbersJan 17, 2008
  30. Linus TorvaldsJan 17, 2008
  31. Pascal ObryJan 17, 2008
  32. Johannes SchindelinJan 17, 2008
  33. Pascal ObryJan 17, 2008
  34. Paul UmbersJan 17, 2008
  35. Alex RiesenJan 17, 2008
  36. Nicholas WourmsJan 17, 2008
  37. Alex RiesenJan 17, 2008
  38. Paul UmbersJan 16, 2008
  39. Pascal ObryJan 15, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.