bug-libtool
[Top][All Lists]
Advanced

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

bug#17802: Possible libtool bug in func_convert_core_msys_to_w32


From: Peter Rosin
Subject: bug#17802: Possible libtool bug in func_convert_core_msys_to_w32
Date: Thu, 19 Jun 2014 00:11:20 +0200
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0

On 2014-06-18 17:30, Franchuk Alex (Alex) wrote:
> Hi,
> 
> I believe there is a bug in the function func_convert_core_msys_to_w32,
> as "cmd //c" opens a command prompt and then hangs on Windows 7,
> preventing the caller from going any further, whereas if you change this
> to "cmd /C", it works as intended. Not sure if older windows systems
> worked with //c, but Win7 definitely doesn't.

We're missing context. "cmd //c" is intended to be executed from MSYS
(function named ...msys_to_w32 remember) and the MSYS command line
parsing heuristic is supposed treat //c as if you really wanted to say /c.

And that works for me on Windows 7:

$ cmd //c type 'C:\MinGW\msys\1.0\bin\cmd'
#!/bin/sh
# Copyright (C) 2002, Earnie Boyd
#   mailto:do not feed the spammers
# This file is part of Minimal SYStem.
#   http://www.mingw.org/msys.shtml
# File: cmd

"$COMSPEC" "$@"
$ uname -s
MINGW32_NT-6.1


So, I'm wondering in what context your func_convert_core_msys_to_w32 is
running?

Cheers,
Peter





reply via email to

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