[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 2.2.7a: unresolved external symbol _lt_libltdlc_LTX_preloaded_symbol

From: Roumen Petrov
Subject: Re: 2.2.7a: unresolved external symbol _lt_libltdlc_LTX_preloaded_symbols
Date: Thu, 27 Nov 2008 23:30:09 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20081114 SeaMonkey/1.1.13

Peter Rosin wrote:
Den 2008-11-27 21:17, skrev Matthieu Nottale:
Peter Rosin wrote:
I don't think Wine does such path translations anyway, but I'm not a
Wine user, so don't take my word for it...
On the contrary, wine does a great job at this.


The problem is that cl.exe does not understand that an argument starting with / is a file path. Likely since / is its option marker:

Which just shows me that Wine does it too late for this case (probably
in CreateFile instead of the heuristic MSYS is using when it adjusts
process arguments), so Wine is not perfect. And there is no perfect
solution to this issue, MSYS gets it wrong sometimes, and Wine gets it
wrong sometimes (no, I'm in no way advocating that Wine should somehow
adopt the argument mangling strategy used by MSYS).

And you really can't blame cl for this, it's a Wine problem. / is very
much documented as the cl option marker (what a brain fart that is, but
luckily the dash works equally well), so you better use \ if you need
to pass rooted paths w/o drive letters (has to be rare on Windows). But
that piece of advice doesn't help Wine users much of course...


It is not wine job to translate command line arguments. By example on my file system exist directory /V and what to expect from wine if for a program this is valid command line argument. libtool do path translation before to create wrapper executable (cygwin mingw host_os).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]