X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.2 required=5.0 tests=AWL,BAYES_00,DKIM_ADSP_NXDOMAIN,SPF_HELO_PASS,TW_SV,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Mail-Followup-To: cygwin@cygwin.com To: cygwin@cygwin.com From: Gary Subject: Re: svn Date: Tue, 15 Feb 2011 12:09:21 +0100 Lines: 20 Message-ID: References: <4D540927.9030000@cs.umass.edu> <83vd0rmzd6.fsf@garydjones.name> <4D54506B.7080702@acm.org> <4D5563A9.60607@acm.org> <4D596749.7000708@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (cygwin) X-No-Archive: Yes Mail-Copies-To: never X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com David Rothenberger wrote: > On 2/14/2011 12:11 AM, Gary wrote: >> If I can replace svn in the sequence with something else, for example >> tortoise, and everything then works, then Cygwin/svn *is* the culprit. > > If the bits are identical, then what else could be breaking your build? > Perhaps the permissions on files, as I suggested in the same email you > partially quoted above? You said: > [if bytes identiocal] I can't see how svn could be the culprit. > > Unless perhaps the permissions on some of the DLLs are different. It > might be worth using cacls to inspect the ACLs on some of the DLLs. I could't comment on that, because I hadn't had time to try it out. They are different - the files checked out with Tortoise correctly (I guess) have the various EXECUTE flags set, those with Cygwin's svn do not. -- 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