Re: 2.2.7a: unresolved external symbol _lt_libltdlc_LTX_preloaded_symbols

[Peter Rosin]

Den 2008-11-27 22:30, skrev Roumen Petrov:
> Peter Rosin wrote:
*snip*
> > 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...
> >
> > Cheers,
> > Peter
>
> 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.

I never said it was Wine's job. On the contrary, I said that Wine should
*not* adopt the argument mangling stategy used by MSYS. So we are violently
agreeing. I was only trying to point out that Wine does not solve all
path translation issues in libtool.

> libtool do path translation before to create wrapper executable (cygwin 
> mingw host_os).

Yes, but the problem is how to infer on what arguments (and what part of
arguments in some cases) path translation is required. The actual path
translation mechanics is easy (sorry Charles, no disrespect for your work
implied), the hard part is /when/ to make use of it.

Cheers,
Peter