X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0	tests=AWL,BAYES_00,SPF_HELO_PASS,TW_YG,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Vadim Zeitlin <vz-cygwin AT zeitlins DOT org>
Subject: Re: Bug with paths containing double slashes after double dot after a mount point
Date: Sat, 18 Jun 2011 14:41:56 +0000 (UTC)
Lines: 23
Message-ID: <loom.20110618T163638-192@post.gmane.org>
References: <E1QXeGw-0005zV-5X AT smtp DOT tt-solutions DOT com> <4DFBC1D2 DOT 4090207 AT ronin-capital DOT com> <loom DOT 20110617T231522-545 AT post DOT gmane DOT org> <4DFBCCB7 DOT 2080408 AT sbcglobal DOT net> <loom DOT 20110618T002902-783 AT post DOT gmane DOT org> <D255ECB130623742B0975B8F16C166C3578C1C3B56 AT LM-EXCHANGE DOT lifemodeler DOT com> <20110618083139 DOT GL3437 AT calimero DOT vinschen DOT de> <loom DOT 20110618T131403-874 AT post DOT gmane DOT org> <20110618113346 DOT GN3437 AT calimero DOT vinschen DOT de> <4DFCAF62 DOT 2010006 AT cwilson DOT fastmail DOT fm>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

Charles Wilson <cygwin <at> cwilson.fastmail.fm> writes:

> On 6/18/2011 7:33 AM, Corinna Vinschen wrote:
> > cygpath -pm `some-mingw-g++ -print-search-dirs`
> 
> As the OP stated, this is happening deep inside libtool, so it's not
> like he can easily insert a call to 'cygpath' in there.  Now, libtool
> DOES have some limited support for environments where path formats
> differ between the build system and the compiler -- specifically, for
> using the native mingw gcc from cygwin -- but you have to take some
> special steps to activate it.

 Thanks for the links, I didn't know about this but it looks like exactly
what I should be doing and I'll test it a.s.a.p.

 And in the longer term I'll try to switch to i686-w64-mingw32
cross-compiler (I can't use i686-pc-mingw32 one because it uses DW2
exceptions while I really need SJLJ ones for catching exceptions from GUI
message handlers).

 Thanks again for the libtool hint and to Corinna for fixing the bug!
VZ



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