Problem building CVS-1.10.x

[Steven N. Hirsch]

On Tue, 28 Dec 1999, Trevor Forbes wrote:

> Steve,
> 
> Not that this helps your compiling problem but do you realise that the
> Cygwin client binaries (I have only used the CD ver) will handle Unix-based
> source-code, i.e. no end-of-line conversion.

Hi Trevor,

It handles the sources in the sense that it can read them and compare with
the repository.  However, initial module checkout (and new items picked up
on global update operations) creates files in Dos/Win eol format.  This
means a separate operation with dos2unix before they are palatable to my
Linux environment.  

I can't make sense of the error message cvs gives me with the cvs builds.
Very annoying.

> I use (on Win2k, fat32) the std CD version of cvs (Ver 1.10)  with pserver
> and SSH (Ver 1.2.27) from Sergey Okhapkin site.

What do you mean "std CD version"?  Just curious.

Steve


> > All,
> >
> > This one's got me stumped, and I cannot find anything relevant in the
> > archives.  I need to build a version of CVS 1.10.x which will properly
> > handle Unix-based source-code, i.e. no end-of-line conversion.  Step one
> > was to build CVS "out of the box" for a baseline.  Unfortunately, I'm
> > unable to construct a working copy!  I seem to remember being able to do
> > this last year, and I have numerous per-compiled binaries from the net to
> > prove it's possible.
> >
> > The build proceeds without any errors, but whenever I try to checkout
> > anything from a remote repository (using pserver), this error occurs:
> >
> > cvs.exe [checkout aborted]: writing to server: The descriptor is a file,
> > not a socket
> >
> > This is consistant across three different versions of CVS, 1.10, 1.10.5
> > and 1.10.7.1 (latest and greatest).  The message is emitted by a section
> > of code which attempts to flush a buffer back to the server (in client.c,
> > I believe).  Basic communication between client and server is happening,
> > since I'm able to do the initial cvs login!
> >
> > I can't see anything overtly wrong with the subject code, and no one else
> > seems to have this problem.  Any hints as to what's wrong?
> >
> > Again, using any of the pre-compiled binaries under Cygwin works just
> > fine.  So, it's _not_ a setup or user problem.
> >
> > Steve
> >
> >
> >
> > --
> > Want to unsubscribe from this list?
> > Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> >
> >
> 


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com