From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin@cygwin.com
Subject: Re: Bug with paths containing double slashes after double dot after a mount point
Date: Sat, 18 Jun 2011 14:00:00 -0000 [thread overview]
Message-ID: <4DFCAF62.2010006@cwilson.fastmail.fm> (raw)
In-Reply-To: <20110618113346.GN3437@calimero.vinschen.de>
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. (By default, when libtool is configured,
it naturally assumes that --build=i686-pc-cygwin --host=i686-pc-mingw32
means 'use the cygwin-hosted mingw cross compiler' and does NOT activate
this path support for the tools, because it is assumed the toolchain
itself understands cygwin paths).
See
info libtool 'Cross compiling'
info libtool 'File name conversion'
info libtool 'Cygwin/Windows File Name Conversion'
and finally
info libtool 'Cygwin to MinGW Cross'
(you want the 'fake' scenario).
Basically, what you have to do is this:
export lt_cv_to_tool_file_cmd=func_convert_file_cygwin_to_w32
export PATH="/c/MinGW/bin:${PATH}"
configure --build=i686-pc-cygwin \
--host=mingw32 \
NM=/c/MinGW/bin/nm.exe
Which does a number of things: (1) it activates the filename conversion
logic but ONLY for the paths that libtool feeds to the compiler tools,
(2) it ensures that the mingw.org compiler is used by forcing the name
'mingw32-gcc.exe' etc, and (3) ensures that the other mingw utilities
are found first in the PATH. (4) Finally, there's something special
about $NM, but I forget what.
> Other than that, I fixed that in CVS. It's a Win32 path coversion problem
> which only occurs if there are multiple backslashes trailing a ".." path
> component.
Yay!
--
Chuck
--
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
next prev parent reply other threads:[~2011-06-18 14:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 19:00 Vadim Zeitlin
2011-06-17 21:07 ` Illia Bobyr
2011-06-17 21:23 ` Vadim Zeitlin
2011-06-17 21:53 ` Greg Chicares
2011-06-17 22:32 ` Vadim Zeitlin
2011-06-17 23:30 ` Fahlgren, Eric
2011-06-18 8:32 ` Corinna Vinschen
2011-06-18 11:18 ` Vadim Zeitlin
2011-06-18 11:34 ` Corinna Vinschen
2011-06-18 13:44 ` Vadim Zeitlin
2011-06-18 15:56 ` Corinna Vinschen
2011-06-18 14:00 ` Charles Wilson [this message]
2011-06-18 14:42 ` Vadim Zeitlin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DFCAF62.2010006@cwilson.fastmail.fm \
--to=cygwin@cwilson.fastmail.fm \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).