Message-ID: <4D540927.9030000@cs.umass.edu>
Date: Thu, 10 Feb 2011 10:49:59 -0500
From: Eliot Moss <moss@cs.umass.edu>
Reply-To: moss@cs.umass.edu
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: svn
References: <ij1160$346$1@dough.gmane.org>
In-Reply-To: <ij1160$346$1@dough.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 2/10/2011 10:45 AM, Gary wrote:
> Not sure if this is a Cygwin-svn problem or just a svn-is-just-f*cked-up
> problem.
>
> I use the Cygwin command line interface - svn, version 1.6.15 (r1038135)
> compiled Nov 29 2010, 14:09:28 - and was having problems compiling a
> modified, checked out project, against some dlls also kept in the
> repo. No matter what, VC# was unable to build a release version, and the
> debug versions it built seemed to be "somewhat flaky".
>
> Today I installed and used TortoiseSVN (*spit*) Version 1.6.12, checked
> out the project, and was able to build painlessly.
>
> So, is this just Subversion and it's normal version incompatibility
> crap, or some problem with the Cygwin build, does anyone know?

No particular idea, but I wonder if it has to do with
(a) what svn believes to be a text, as opposed to binary, file;
(b) how you have cygwin set to treat text files; and
(c) what line terminator, etc., VC# wants to see.

Regards -- Eliot Moss

--
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