Subject: Re: bug#14022: libtool-gug

From: Peter Rosin <[email-masked]>
Date: Fri, 22 Mar 2013 08:14:16 +0100

Hi Andreas!

On 2013-03-21 15:41, Andreas Otto wrote:
> Hi,
> 
> the following code has an error:

I don't think so, see below...

> # func_convert_core_msys_to_w32 ARG
> # Convert file name or path ARG from MSYS format to w32 format. Return
> # result in func_convert_core_msys_to_w32_result.
> func_convert_core_msys_to_w32 ()
> {
>   $opt_debug
>   # awkward: cmd appends spaces to result
>   func_convert_core_msys_to_w32_result=`( cmd //c echo "$1" ) 2>/dev/null |
>     $SED -e 's/[ ]*$//' -e "$lt_sed_naive_backslashify"`
> }
> #end: func_convert_core_msys_to_w32
> 
> I need "...cmd /c ..." to get my stuff compiled

*snip*

> $ cygpath -V
> cygpath (cygwin) 1.7.17

cygpath? If you are reporting the cygpath version and say that
you need "...cmd /c..." instead of "...cmd //c...", then it
sounds as if you have confused MSYS and Cygwin. The function
func_convert_core_msys_to_w32 should only be used when you
are using MSYS. It's not for Cygwin.

On Cygwin, it is best to use a Cygwin-hosted cross compiler.
If you want to run a MinGW-hosted compiler, it's best to
use MSYS. But you still can (if you obey the rules) use
a MinGW-hosted compiler from Cygwin, but in that case you
want to use func_convert_file_cygwin_to_w32.

My advise is that you read this chapter carefully:
http://www.gnu.org/software/libtool/manual/libtool.html#File-name-conversion

Cheers,
Peter