latest cygwin: 'run' problem
Gerry Reno
greno@verizon.net
Sat Sep 6 01:49:00 GMT 2014
On 09/05/2014 09:14 PM, Gerry Reno wrote:
> On 09/03/2014 03:48 PM, Achim Gratz wrote:
>> Gerry Reno writes:
>>> On the 32-bit system cygwin installs that haven't been updated yet 'run.exe' shows:
>>>
>>> $ ls -l /usr/bin/run.exe
>>> -rwxr-xr-x 1 Administrator None 65053 Jul 24 2013 /usr/bin/run.exe
>>>
>>> On a 32-bit system with this latest cygwin 'run.exe' shows:
>>>
>>> $ ls -l /usr/bin/run.exe
>>> -rwxr-xr-x 1 SYSTEM SYSTEM 66077 Jun 9 13:16 /usr/bin/run.exe
>>>
>>> Filesize is different so something has changed there.
>> A "cygcheck -f /usr/bin/run.exe" would be more enlightening, although I
>> think the two versions of run should be 1.3.0 and 1.3.1. If so then the
>> reason for mstsc not recognizing the options would be the patch by Max
>> Polk that quotes all the arguments (the change description said it'd
>> quote only arguments with spaces in them, but the code actually quotes
>> all of them anyway). This also means that mstsc seems to implement its
>> own version of options processing or argument quoting (probably the
>> former since options to mstsc need not be quoted). The quoting function
>> in the current version of run is too naive anyway, so I'll have to
>> update it with something more sensible. It'll be a few days, sorry for
>> the inconvenience.
>>
>>
>> Regards,
>> Achim.
> Can run-1.3.0-1 be added back into the Setup as an alternate choice until 'run' can be fixed?
>
> Gerry
>
To clarify this request a bit:
Both run-1.2.0-1 and 1.3.1-1 are broken. Neither one properly runs a command.
The only recent package that actually worked was run-1.3.0-1.
Gerry
--
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
More information about the Cygwin
mailing list