From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25508 invoked by alias); 30 Mar 2015 14:54:34 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 25417 invoked by uid 89); 30 Mar 2015 14:54:34 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.5 required=5.0 tests=AWL,BAYES_20,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mail.voltage.com Received: from mail.voltage.com (HELO mail.voltage.com) (71.6.108.2) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Mon, 30 Mar 2015 14:54:31 +0000 Received: from HQMAILSVR02.voltage.com (unknown [172.16.0.6]) by mail.voltage.com with smtp (TLS: TLSv1/SSLv3,128bits,AES128-SHA) id 6f7d_2a83_54450b09_6222_4914_b83b_0ca3c3e9f336; Sun, 29 Mar 2015 23:51:55 -0700 Received: from HQMAILSVR02.voltage.com ([::1]) by HQMAILSVR02.voltage.com ([::1]) with mapi; Mon, 30 Mar 2015 07:54:29 -0700 From: Phil Smith To: "cygwin@cygwin.com" Date: Mon, 30 Mar 2015 15:35:00 -0000 Subject: RE: Possible chmod problem with a path [WARNING: SPF validation failed] Message-ID: <84BCCD71182F0046BCD2FB054FE52379197703FDF7@HQMAILSVR02.voltage.com> References: <84BCCD71182F0046BCD2FB054FE52379197703FDDD@HQMAILSVR02.voltage.com> <131547857.20150330172345@yandex.ru> In-Reply-To: <131547857.20150330172345@yandex.ru> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes X-SW-Source: 2015-03/txt/msg00524.txt.bz2 Thanks for the reply. Some thoughts: >Please use Cygwin paths with Cygwin tools. >Windows paths are not guaranteed to work with every Cygwin tool. This is scripted, and while I can hack it to use Cygwin paths, it probably = shouldn't be lying to me, saying that it worked. And it did work before, st= ill does with older Cygwin (on another machine). >What you are doing may or may not work, depends, if you are using Cygwin or >native Subversion client. >In either case, it isn't very bright idea to enforce POSIX access mask out= side >Cygwin tree, unless you know what you are doing and absolutely need it. >From your description, you don't need it at all. I'm not actually trying to enforce POSIX anything--I'm trying to be able to= read the build artifacts, which were put there via mv and cp. The compiler= is native Windows, isn't creating the artifacts with any special permissio= ns. So there's actually another mystery, which is why the artifacts don't h= ave the right permissions in the first place. With the cobbled-together env= ironment (CMake, the Dignus compiler, Cygwin) this may not be really diagno= sable, I realized. I was hoping that there was some clue in the fact that t= he path makes a difference. SVN client is Tortoise. I have done a fresh checkout and the problem persists, so it isn't some wei= rdness with a tainted file in the source tree, I don't think. -- 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