Hi,
I'm trying to use ProcessBuilder to execute cygwin programs.
ProcessBuilder is a Java API to run command lines.
The problem I'm dealing with is that redirecting the stdout (or stderr) of a
cygwin program to a file in append mode doesn't work.
The file is not written.
If I do the same with
>On Jan 17 16:19, Corinna Vinschen wrote:
>> On Jan 17 14:16, Pierre Bogossian wrote:
>> > rsh doesn't seem to work anymore since I upgraded to cygwin-1.5.19-2.
>> > Running a simple commande like "rsh localhost echo blah" just hangs
>> > forev
rsh doesn't seem to work anymore since I upgraded to cygwin-1.5.19-2.
Running a simple commande like "rsh localhost echo blah" just hangs forever.
I can't tell if the problem comes from rsh command or from the server, in the
tests I made both were running on the same machine that I updated to 1.5.1
>I never noticed the double ++ and --, but it happens for me too.
>Removing the code to handle KP_Add and KP_Subtract (as the patch
>suggests) may end up breaking the shift+ shift- font changer.
Yes, indeed, I'm using a patched version of libW11 and the shift+
and shift- shortcuts don't work anymo
When rxvt is executed with libW11, there is an annoying bug: each time the
KP_Subtract (or KP_Add) key is pressed, the '-' (or '+') character is
sent two times to the terminal.
This bug has already been reported two years ago, and someone even proposed
a patch:
http://sourceware.org/ml/cygwin/2003
David Reid wrote:
>I'm using rsh to run a command on a remote machine.
>But I only get output back from stderr, not from
>stdout. Here is my sample program and the output:
>
> main() {
> fprintf(stdout, "stdout\n");
> fprintf(stderr, "stderr\n");
> }
>
> $ rsh machine1 ./main
>
>I guess the problem comes from that I'm running Windows NT 4 SP6, which
>have a too old version of shell32.dll...
Indeed, a search on google told that SHGetSpecialFolderPathA exists as
of shell32.dll version 4.71 while the version on my system is 4.00.
Pierre
--
When I run cygpath with the new 1.5.6 release, an error window pops up
saying that the entry point for SHGetSpecialFolderPathA can't be found
in SHELL32.DLL.
I also tried the latest snapshot but I had the same message.
I guess the problem comes from that I'm running Windows NT 4 SP6, which
have a
>Here's a snippet from `cat /proc/cpuinfo`:
>
>vendor id : GenuntelineI
>
>This should read GenuineIntel
It seems that cygwin doesn't like AMD processors neither:
vendor id : AuthcAMDenti
Pierre
--
___
9 matches
Mail list logo
