From: Wyss Clemens <WYS@...>
Date: 2001-07-04T23:26:39+09:00
Subject: [ruby-talk:17236] Re: "cvs commit" from within ruby

Oops, it was not the cygwin1.dll neither.
I had to put the cygwin shell ("sh.exe") into one of the directories of PATH
and everything worked fine (even for my colleagues which do not have
cygwin-tools installed).

Clemens

> -----Urspr�ngliche Nachricht-----
> Von: Clemens Wyss [mailto:wys@helbling.ch]
> Gesendet am: Freitag, 29. Juni 2001 22:45
> An: ruby-talk@ruby-lang.org
> Betreff: [ruby-talk:17089] Re: "cvs commit" from within ruby
> 
> ts <decoux@moulon.inra.fr> wrote in
> news:pC2%6.98962$yz5.4120369@e420r-sjo2.usenetserver.com: 
> 
> >>>>>> "C" == Clemens Wyss <wys@helbling.ch> writes:
> > 
> > C> the ruby1.6.3-1.exe installable and the WinCvs1.2-cvs. My
> > implication C> therefore is that the ruby1.6.3-build ((2001-03-19)
> > [i386-cygwin]) causes C> the "problem". 
> > 
> >  Perhaps a problem with the cygwin build
> > 
> 
> Not the build, but the cygwin1.dll. When exchanging it with 
> the cygwin1.dll 
> of the cygwin-tools, everything worked as expected.
> Dave (or Andrew) would you mind adding the latest-greatest 
> cygwin1.dll to 
> your next windows installable (ruby1.6.3-2.exe or so)?
> Have a nice weekend and thanks for the advices
> Clemens
>