Re: [Mingw-users] bash-3.1-MSYS-1.0.11 under wine

[Charles W. <cwi...@us...>]

Keith Marshall wrote:
> I gave up on RXVT long ago, simply because its 

you mean MSYS's and cygwin's?  rxvt does not emulate ptys, the 
underlying posix DLL does that.

> broken pty emulation 
> caused me too much grief.  (And yes, I too found Cygwin's RXVT to be 
> similarly broken; the difference is that Cygwin doesn't push RXVT as 
> the default console).

Keith, you really don't have to jump in and trash rxvt Every. Single. 
Time. it is mentioned.  Everybody already knows you don't like it.

As the cygwin maintainer of rxvt, I'd appreciate it if, when you do 
trash it, you point out that the pty problem is NOT the fault of rxvt. 
ANY terminal emulator that links against the cygwin dll or the msys dll 
will use that DLL's pty emulation.  And the culprit here is the failure 
of the posix DLLs to implement PTYs in a way compatible with native 
win32 apps -- like mingw gcc.)

Anyway, rxvt has *nothing* to do with this thread, aside from the fact 
that Earnie mentioned it in passing.

The problem in *this* thread, is invoking a (native) win32 executable on 
a linux box via wine. That executable itself is just a wrapper, that 
attempts to exec a posix shell (e.g. msys-bash) with a shell script 
argument.  This was the original failure case.  But the OP simplified it 
down to just invoking msys bash via wine.

 From the OP:
> If executable is run for linux command prompt:
> $ wine bash.exe --help; echo $?
> 1
> 
> 
> Also from wine command prompt:
> $ wine cmd
> CMD Version 0.9.24
> 
> ...\bin>bash.exe --help
> ...\bin>
> and command output nothing.


No rxvt involved.

Might be the same underlying pty cause, though.  On the other hand, I 
can run (msys) "bash.exe --help" from a regular WindowsXP cmd.exe and it 
works just fine.  So maybe the problem is wine.

But it sure isn't rxvt.

--
Chuck