From: Gary <cygwin@garydjones.name>
To: cygwin@cygwin.com
Subject: svn
Date: Thu, 10 Feb 2011 15:45:00 -0000 [thread overview]
Message-ID: <ij1160$346$1@dough.gmane.org> (raw)
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?
--
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
next reply other threads:[~2011-02-10 15:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 15:45 Gary [this message]
2011-02-10 15:50 ` svn Eliot Moss
2011-02-10 20:03 ` svn Gary
2011-02-10 20:54 ` svn David Rothenberger
2011-02-11 8:09 ` svn Gary
2011-02-11 12:01 ` svn Eliot Moss
2011-02-11 16:28 ` svn David Rothenberger
2011-02-14 8:12 ` svn Gary
2011-02-14 12:01 ` svn Eliot Moss
2011-02-14 12:25 ` svn Gary
2011-02-14 14:37 ` svn Eliot Moss
2011-02-14 14:44 ` svn Gary
2011-02-14 16:18 ` svn Eliot Moss
2011-02-14 17:33 ` svn David Rothenberger
2011-02-15 11:09 ` svn Gary
2011-02-15 16:16 ` svn David Rothenberger
2011-02-11 2:15 ` svn Eliot Moss
2011-02-11 4:20 ` svn Larry Hall (Cygwin)
2011-02-11 4:21 ` svn Eliot Moss
2011-02-11 7:24 ` svn Gary
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ij1160$346$1@dough.gmane.org' \
--to=cygwin@garydjones.name \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).