Alex Riesen wrote:
quoted text
> Paul Umbers, Wed, Jan 16, 2008 22:44:10 +0100:
>> Here's the log from the latest strace.
> 
> Something is fishy here (aside from the horrible selection of
> information in the trace output):
> 

That is a matter of opinion. Besides, Cygwin's strace was designed first and
foremost with debugging the Cygwin dll in mind. Perhaps the choice of name for
the utility was a poor one, since it implies that it ought to be the same as
the official strace.

As for the matter at hand:

First, *you must* make sure you inspect every directory in your PATH for other
copies of cygwin1.dll. Sometimes, without telling you, other software packages
will distribute the cygwin1.dll. Often times this is an older version of that
dll. If there are any these found outside of the Cygwin installation tree, you
must remove them from your PATH.

Secondly, reinstalling Cygwin by rerunning setup is not enough. Cygwin is
pretty self-contained and non-invasive (contrary to the popular FUD spread by
MinGWists), but it does have 2 Registry keys which should be axed if you want a
clean install. They are:

HKEY_CURRENT_USER\Software\Cygnus Solutions
HKEY_LOCAL_MACHINE\Software\Cygnus Solutions

Lastly, has the user actually tried reporting this problem to
"cygwin@cygwin.com"? That is the proper list for reporting problems with
official cygwin packaged applications. Both the maintainer of the "git" Cygwin
package and the core Cygwin developers monitor that list, so you are much more
likely to get a solution to your problem there. Nevertheless, it does seem that
in this case it might be a problem with git's handling of failures to create
hard links. But do keep this in mind for future reference.

Cheers,
Nicholas
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html