From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20061 invoked by alias); 25 Jan 2014 21:18:08 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 20052 invoked by uid 89); 25 Jan 2014 21:18:07 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: qmta01.emeryville.ca.mail.comcast.net Received: from qmta01.emeryville.ca.mail.comcast.net (HELO qmta01.emeryville.ca.mail.comcast.net) (76.96.30.16) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 25 Jan 2014 21:18:05 +0000 Received: from omta16.emeryville.ca.mail.comcast.net ([76.96.30.72]) by qmta01.emeryville.ca.mail.comcast.net with comcast id JMF61n0021ZMdJ4A1MJ4vg; Sat, 25 Jan 2014 21:18:04 +0000 Received: from mail.daveroth.dyndns.org ([67.168.153.247]) by omta16.emeryville.ca.mail.comcast.net with comcast id JMJ31n0045LXggb8cMJ3we; Sat, 25 Jan 2014 21:18:04 +0000 Received: from [10.249.1.105] (fee.daveroth.dyndns.org [10.249.1.105]) by mail.daveroth.dyndns.org (8.14.4/8.14.4/Debian-4) with ESMTP id s0PLI1gF019769 for ; Sat, 25 Jan 2014 13:18:01 -0800 Message-ID: <52E42A1F.3010305@acm.org> Date: Sat, 25 Jan 2014 21:18:00 -0000 From: David Rothenberger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Maintainer for git? References: <20140115105534.GB31912@tastycake.net> <20140123105142.GN2357@calimero.vinschen.de> <20140125115958.GU2357@calimero.vinschen.de> In-Reply-To: <20140125115958.GU2357@calimero.vinschen.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.com X-SW-Source: 2014-01/txt/msg00415.txt.bz2 On 1/25/2014 3:59 AM, Corinna Vinschen wrote: > On Jan 23 11:51, Corinna Vinschen wrote: >> On Jan 22 16:42, Chris O'Bryan wrote: >>>> On Mon, Jan 20, 2014 at 5:31 PM, Steven Penny wrote: >>>> >>>>> Are you certain the bug is present in Adam’s version? He >>>>> has tested it here >>>>> >>>>> http://cygwin.com/ml/cygwin/2014-01/msg00085.html >>>> >>>> I just tried cloning something big again (the linux kernel). >>>> See below. The first one was with git-1.7.9 the default >>>> Cygwin version. [...] x86$ git clone >>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git >>>> >>>> linux-git-1.8.5.2 >>>> Cloning into 'linux-git-1.8.5.2'... remote: Counting objects: >>>> 3366700, done. remote: Compressing objects: 100% >>>> (508113/508113), done. remote: Total 3366700 (delta 2833563), >>>> reused 3362434 (delta 2829537) Receiving objects: 100% >>>> (3366700/3366700), 703.64 MiB | 2.16 MiB/s, done. fatal: pack >>>> is corrupted (SHA1 mismatch) fatal: index-pack failed [...] >> >> Even if it's an OpenSSL issue, I'm not sure what to do about it. >> I'm building OpenSSL for Cygwin, but I have no knowledge of the >> crypto stuff... >> >> I don't see anything unusual in the build process, except, maybe, >> that for SHA1 the x86 assembler code is used. I'm wondering what >> happens when taking out -DSHA1_ASM from the build process. Or >> what happens when using -O2 instead of -O3. > > I have a hunch that this is not a OpenSSL but a Cygwin problem. > > The default case in OpenSSL is to use SSE2 instructions in the x86 > assembler code. However, SSE2 instructions utilize the x86 XMM > registers, which are not saved and restored in setjmp/longjmp, nor > are they stored and restored in signal handling under Cygwin. > > In the long run Cygwin should save and restore the XMM registers > on x86 as well, I guess. > > For the time being, I've build a new OpenSSL version 1.0.1f-2 with > the "no-sse2" flag. With this version I could clone the linx repo > without error. Please give it a try. The new OpenSSL version fixes things for me. This explanation makes sense given what I've seen as well. I had built my own updated git binaries a while ago. I noticed that for x86, the binaries would fail cloning a large repository, and would also give spurious errors from "git fsck" on an existing repository. I had no such problems with my x86_64 build. With the new OpenSSL on x86, both the clone and the fsck problems have gone away. Thanks! Now my colleagues can use Git 1.8 with x86! -- David Rothenberger ---- daveroth@acm.org Revolution, n.: In politics, an abrupt change in the form of misgovernment. -- Ambrose Bierce -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple