Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Mon, 27 Dec 1999 11:17:39 -0500 (EST)
From: "Steven N. Hirsch" <shirsch AT adelphia DOT net>
X-Sender: hirsch AT pii DOT fast DOT net
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Problem building CVS-1.10.x
Message-ID: <Pine.LNX.4.10.9912271108150.2251-100000@pii.fast.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

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 AT sourceware DOT cygnus DOT com