X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 22 Jan 2010 10:45:51 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Design issue with new MS-DOS style path warning? Message-ID: <20100122154551.GB4020@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <81D39E818991E549B1F66EB6A7D18422BE8626 AT AVSMOEXCL02 DOT activision DOT com> <4B57DF25 DOT 4040605 AT gmail DOT com> <7f95d3561001220517k4fd93c6btdda02fd06596e97f AT mail DOT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7f95d3561001220517k4fd93c6btdda02fd06596e97f@mail.gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 02:17:56PM +0100, Eric Vautier wrote: >It may be good advice not to do it. > >However, there's the case of environment variables, or parameter files >containing Windows-style paths used in build.xml, for example. It >appears that those variables are not converted sometimes, resulting in >failures. Cygwin doesn't complain about MS-DOS paths in random environment variables unless your program decides to use them to open/stat/access/etc. a file. If you are getting warnings then Cygwin is working as designed. It 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. >One of my build files refers to such a property. And the "property" is? >I get the DOS file warning at the start of the script, and further >down, an error states that C:/cygdrive/c/Users/... couldn't be found. >I wonder how Cygwin would come to creating such a hybrid path. Did >anyone else run into this? The same script worked perfectly fine >before I upgraded to 1.7. It is likely that Cygwin didn't. It's much more likely that it is something local to your installation. If it wasn't then the mailing list would be full of complaints. cgf -- 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