public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Rothenberger <daveroth@acm.org>
To: cygwin@cygwin.com
Subject: Re: svn
Date: Tue, 15 Feb 2011 16:16:00 -0000	[thread overview]
Message-ID: <4D5AA6D0.20201@acm.org> (raw)
In-Reply-To: <ijdmt3$jiu$1@dough.gmane.org>

On 2/15/2011 3:09 AM, Gary wrote:
> 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.

If those files have the svn:executable property set, then it's a bug in
Cygwin's svn. Otherwise, you just need to set that property on the DLLs.
Maybe TortoiseSVN does some special handling for DLLs.

-- 
David Rothenberger  ----  daveroth@acm.org

The Public is merely a multiplied "me."
                -- Mark Twain

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

  reply	other threads:[~2011-02-15 16:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10 15:45 svn Gary
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                 ` David Rothenberger [this message]
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=4D5AA6D0.20201@acm.org \
    --to=daveroth@acm.org \
    --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).