From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16915 invoked by alias); 18 Jun 2011 14:42:24 -0000 Received: (qmail 16887 invoked by uid 22791); 18 Jun 2011 14:42:22 -0000 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 Received: from lo.gmane.org (HELO lo.gmane.org) (80.91.229.12) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 18 Jun 2011 14:42:07 +0000 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QXwis-0004nK-KD for cygwin@cygwin.com; Sat, 18 Jun 2011 16:42:06 +0200 Received: from 85-168-18-34.rev.numericable.fr ([85.168.18.34]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 18 Jun 2011 16:42:06 +0200 Received: from vz-cygwin by 85-168-18-34.rev.numericable.fr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 18 Jun 2011 16:42:06 +0200 To: cygwin@cygwin.com From: Vadim Zeitlin Subject: Re: Bug with paths containing double slashes after double dot after a mount point Date: Sat, 18 Jun 2011 14:42:00 -0000 Message-ID: References: <4DFBC1D2.4090207@ronin-capital.com> <4DFBCCB7.2080408@sbcglobal.net> <20110618083139.GL3437@calimero.vinschen.de> <20110618113346.GN3437@calimero.vinschen.de> <4DFCAF62.2010006@cwilson.fastmail.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@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-06/txt/msg00232.txt.bz2 Charles Wilson 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