X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=le fQVlhSxXscSfsl9VpGRU3nq6j44HGp1HmcXXpzJal7Pp7RFHYDirRj91+p8YmgtW tZdDUEu+q8jwyf0JE5ychtkoT+gyiejCrURSahQg8iNP73zw3azotI9hiiv4f4mk ZdDgX7jshUBiC8fWvyxCHLMIBG+va5EuY08yLmNt8= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=ezkKKZsP cMJuELt+HioQK8IGE60=; b=iv3ktKDCn9owGsT3OC4vU29u9yBFLb9LLoeDqE9I yj2GyI2DMjFhvOmuJXO4wsBFH0Yl7xre+q1vcbeqrnSVoIGAXJbiNbABlDs7LUrH d0dFv9JmkMU/Wwep8QsC171ZkDCOGJ8DaH0VMcAFpXbI3nMXYY73Xzfu3Ld73T6B qig= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-ea0-f169.google.com MIME-Version: 1.0 X-Received: by 10.15.81.196 with SMTP id x44mr18651376eey.31.1390697757793; Sat, 25 Jan 2014 16:55:57 -0800 (PST) In-Reply-To: <20140125115958.GU2357@calimero.vinschen.de> References: <20140115105534 DOT GB31912 AT tastycake DOT net> <20140123105142 DOT GN2357 AT calimero DOT vinschen DOT de> <20140125115958 DOT GU2357 AT calimero DOT vinschen DOT de> Date: Sat, 25 Jan 2014 16:55:57 -0800 Message-ID: Subject: Re: Maintainer for git? From: Balaji Venkataraman To: Cygwin Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes On Sat, Jan 25, 2014 at 3:59 AM, Corinna Vinschen wrote: > 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. Thanks Corinna for the openssl updates. I definitely see an improvement with them. I was able to clone the ffmpeg repo w/o errors - which was not happening earlier. However, the linux repo clone failed w/ the same error as before. Not sure if there is something else that could be going on. x86$ git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git linux Cloning into 'linux'... remote: Counting objects: 3407728, done. remote: Compressing objects: 100% (517899/517899), done. remote: Total 3407728 (delta 2869094), reused 3399100 (delta 2860672) Receiving objects: 100% (3407728/3407728), 713.94 MiB | 619.00 KiB/s, done. fatal: pack is corrupted (SHA1 mismatch) fatal: index-pack failed -- 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