X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=0.1 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<20100122154551.GB4020@ednor.casa.cgf.cx>
References:	<81D39E818991E549B1F66EB6A7D18422BE8626 AT AVSMOEXCL02 DOT activision DOT com> <4B57DF25 DOT 4040605 AT gmail DOT com> <7f95d3561001220517k4fd93c6btdda02fd06596e97f AT mail DOT gmail DOT com> <20100122154551 DOT GB4020 AT ednor DOT casa DOT cgf DOT cx>
Date:	Fri, 22 Jan 2010 17:23:09 +0100
Message-ID:	<7f95d3561001220823md77as48d8128d396c8370@mail.gmail.com>
Subject:	Re: Design issue with new MS-DOS style path warning?
From:	Eric Vautier <eric.vautier+cygwin AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Fri, Jan 22, 2010 at 4:45 PM, Christopher Faylor
<cgf-use-the-mailinglist-please AT cygwin DOT com> wrote:
> On Fri, Jan 22, 2010 at 02:17:56PM +0100, Eric Vautier wrote:
> If you are getting warnings then Cygwin is working as designed. =A0It is
> telling you that you're doing something that is not guaranteed to work.
> If you want to turn this off then use the CYGWIN environment variable.

I understand that.

>>One of my build files refers to such a property.
>
> And the "property" is?

I'll try and investigate the issue further.

>>I get the DOS file warning at the start of the script, and further
>>down, an error states that C:/cygdrive/c/Users/... =A0couldn't be found.
>>I wonder how Cygwin would come to creating such a hybrid path. =A0Did
>>anyone else run into this? =A0The same script worked perfectly fine
>>before I upgraded to 1.7.
>
> It is likely that Cygwin didn't. =A0It's much more likely that it is
> something local to your installation. =A0If it wasn't then the mailing
> list would be full of complaints.

Let me confirm that the script has not changed at all, and used to
work fine under the previous version. You'll agree that arriving at a
C:/cygdrive/c/... path is a little odd, regardless of setup. Perhaps a
string is set that way some place, but I doubt it.
-e

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

- Raw text -