X-Spam-Check-By: sourceware.org Date: Fri, 28 Jul 2006 11:40:50 -0400 From: Bob Rossi To: cygwin AT cygwin DOT com Subject: Re: 3.81 and windows paths Message-ID: <20060728154050.GB4533@brasko.net> Mail-Followup-To: cygwin AT cygwin DOT com References: <44C92033 DOT A2978A8E AT dessent DOT net> <17609 DOT 11132 DOT 462789 DOT 443104 AT lemming DOT engeast DOT baynetworks DOT com> <20060727221136 DOT GD6653 AT trixie DOT casa DOT cgf DOT cx> <17610 DOT 6020 DOT 12729 DOT 506044 AT lemming DOT engeast DOT baynetworks DOT com> <17610 DOT 7126 DOT 60597 DOT 468701 AT segfault DOT lan> <17610 DOT 8103 DOT 778129 DOT 918123 AT lemming DOT engeast DOT baynetworks DOT com> <44CA2188 DOT 9050905 AT equate DOT dyndns DOT org> <20060728144330 DOT GA4533 AT brasko DOT net> <20060728145443 DOT GE16728 AT trixie DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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, Jul 28, 2006 at 11:28:42AM -0400, Igor Peshansky wrote: > On Fri, 28 Jul 2006, Christopher Faylor wrote: > > > On Fri, Jul 28, 2006 at 10:43:30AM -0400, Bob Rossi wrote: > > >> Well, the whole point of cygwin is to give a POSIX-compatible > > >> environment in win32. So it's aiming to be like linux, not windows. > > >> This means that if something like a makefile parses fine in linux, but > > >> not in cygwin (barring linker stuff), something is wrong. > > > > > >Yeah, what's wrong is that cl doesn't accept posix paths. For some > > >reason, they were added, we all got addicted to it, and now it's being > > >ripped out from underneath us. It's not a very friendly thing to do. > > If you are invoking cl in your Makefiles, they are no longer POSIX or > Linux Makefiles, and you might as well run your paths through cygpath > before sending them to cl. Yes, this is the solution I came up with, but it's not an easy task. It's also slightly ugly, since we compile with g++/gcc on other systems. > > > > Hmm, I thought we didn't have an automatic censorship filter on this list. > I guess you just have to be *really* annoyed to trip it. > > OTOH, a simple "here we go again" would probably have > sufficed... At least I understand this. Thanks, Bob Rossi -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/