X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=1.4 required=5.0 tests=AWL,BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Message-ID: <30821005.post@talk.nabble.com> Date: Tue, 1 Feb 2011 13:50:58 -0800 (PST) From: Sunoki To: cygwin AT cygwin DOT com Subject: Re: PATH with spaces In-Reply-To: <4D45AAD7.80807@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <30799162 DOT post AT talk DOT nabble DOT com> <4D456012 DOT 5030107 AT aol DOT com> <4D45AAD7 DOT 80807 AT gmail DOT com> X-IsSubscribed: yes 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 Thanks everyone for the very quick reply... I first did as Vincent advised and installed a make on the cygwin itself... and removed all the reference to the windows program files folder from the path. Then it worked, but I think I will try what you've said Dave, if I find anything useful I will post to the forum! Many thanks! Dave Korn-9 wrote: > > On 30/01/2011 12:56, Tim Prince wrote: >> On 1/30/2011 6:34 AM, Sunoki wrote: >>> >>> $ make >>> cygwin warning: >>> MS-DOS style path detected: /usr/local/bin/C:\Program >>> Preferred POSIX equivalent is: /usr/local/bin/C:/Program >>> CYGWIN environment variable option "nodosfilewarning" turns off this >>> warning. >>> Consult the user's guide for more details about POSIX paths: >>> http://cygwin.com/cygwin-ug-net/using.html#using-pathnames >>> Can't find C:\Program on PATH. > >> Yes, the warning comes about in part due to the use of an unquoted path >> with spaces. > > Not directly it doesn't. My PATH has spaces in it and everything works > just > fine. The shell knows to only separate $PATH at colons. > > That "Can't find" error message doesn't look like anything make itself > would > output to me, and how did /usr/local/bin get concatenated to C:\Program > anyway? (Note that it doesn't have a trailing slash in the path, so > something > has done this deliberately.) > > I think the problem is likely to be that the makefile itself is doing > some > kind of string processing on the PATH, or perhaps that it is being passed > on a > commandline somewhere unquoted and ending up looking like multiple words > to > the receiving program. > > Sunoki, if that isn't enough of a clue to work out what's going wrong, > there's a really useful version of make with a source-level debugger built > in > called 'remake' that you can get from > http://bashdb.sourceforge.net/remake/. > (Last time I checked, it was a straightforward "configure && make && make > install" to build out-of-the-box, so it should be easy to try out if you > want.) > > cheers, > DaveK > > > > -- > 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 > > > -- View this message in context: http://old.nabble.com/PATH-with-spaces-tp30799162p30821005.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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