Hi All,
Well, I solved this, and in case anyone else is interested, here's what I
did. This is certainly inappropriate, but as I don't really know my way
around the configuration process, I can't produce a better patch.
I maunally edited the file "config.h" (after runnning ./configure) to
include the line:
#define USE_SETMODE_BINARY 1
Rebuilt, and all was Good.
Once again, this was on WINNT with the latest cygwin distribution installed.
Cheers,
--Bob
> -----Original Message-----
> From: Bob Whiteside [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 02, 2000 1:00 PM
> To: [EMAIL PROTECTED]
> Subject: Cursed ^M's: latest cygwin, ssh-1.2.27, cvs-1.10.8
>
>
> Hi All,
>
> I'm trying (on winnt) trying to use cvs and ssh.
> Installed the latest
> cygwin stuff. After this, I found (much to my surprised
> delight!) that both
> ssh-1.2.27 and cvs-1.10.8 built just fine! Just the usual ./configure
> followed by make! Nice ... Kudos to the cygwin folks, as well
> as to the
> careful work in ssh and cvs. I know that careful portability
> is not fun (at
> least not to me). Thanks!
>
> Anyway, both of these work just fine separately. ssh behaves
> as I expect,
> and cvs, using a remote CVSROOT like
> "raw@machine:/home/raw/repository" is
> cool.
>
> However, when I try this:
> CVS_RSH=ssh
> CVSROOT=:ext:raw@machine:/home/raw/repository
>
> I get told that cvs got an unrecognized server response
> "ok^M". Sigh. Some
> "friendly" piece of the assembly is inserting a ^M in the
> stream. I can't
> believe it's the remote unix box! Surely ssh wouldn't to
> this. Indeed, if I
> pipe ssh output into od, I don't see any ^M's there.
>
> Thus, I'm currently suspecting something to do with how cvs runs ssh.
> Anyone have a suggestion as to where I should look? Has
> someone else dealt
> with this? I suspect some popen or somesuch isn't giving some
> funky --NO_WEIRD_DOSISMS flag somewhere.
>
> Cheers,
> --Bob
>
>
