Brian Ford wrote:
Incidentally, is there a way to reliably compare two CVS built DLLs from
the cygcheck or uname -a output?
I don't think so, since both just include the date the DLL was built.
FWIW, this problem appears to be fixed by:
http://www.cygwin.com/ml/cygwin/2004-01/msg01160.html
Concu
On Mon, 26 Jan 2004, David Rothenberger wrote:
> Brian Ford wrote:
> > Are you sure this is the latest CVS? It looks like the same problem fixed
> > here to me:
> >
> > http://www.cygwin.com/ml/cygwin/2004-01/msg01140.html
> >
> Yes, I'm sure it is the latest CVS. The problem above is fixed in m
Brian Ford wrote:
Are you sure this is the latest CVS? It looks like the same problem fixed
here to me:
http://www.cygwin.com/ml/cygwin/2004-01/msg01140.html
Yes, I'm sure it is the latest CVS. The problem above is fixed in my
build, but not the problem I reported. It looks the same, but the sh
On Mon, 26 Jan 2004, David Rothenberger wrote:
> I'm having a problem with signals with the latest CVS DLL and ash.
>
> I have a script tst.sh:
>
> #!/bin/sh
> while true; do
> date
> sleep 20
> done
>
>
> >From a cmd.exe prompt, if I do "bash tst.sh"
I'm having a problem with signals with the latest CVS DLL and ash.
I have a script tst.sh:
#!/bin/sh
while true; do
date
sleep 20
done
>From a cmd.exe prompt, if I do "bash tst.sh" and then press Ctrl-C,
the script terminates.
If I do the same with "
5 matches
Mail list logo
