Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3E0A070D.2020107@snet.net> Date: Wed, 25 Dec 2002 14:29:17 -0500 From: Arkadiy Belousov Reply-To: arkadiy AT snet DOT net User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.3a) Gecko/20021212 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael A Chase CC: cygwin AT cygwin DOT com Subject: Re: Bug somewhere between cygwin, gcc and cvs References: <3E09F759 DOT 5040508 AT snet DOT net> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit The version currently available does not support specifying port in CVSROOT. And I need that for ssh tunneling. I do realize I am on the bleeding edge here. Still, it's something to look at when CVS 1.11.2 is ported. Personally, I think it's the compiler. Let's wait till gcc loses (prerelease) label on it. Michael A Chase wrote: >On Wed, 25 Dec 2002 13:22:17 -0500 Arkadiy Belousov wrote: > > > >>I downloaded latest stable CVS code (1.11.2) and compiled it under cygwin. >>"cvs co", "cvs login" and "cvs commit" worked, but not "cvs update". >> >> > >Since you are trying to build a version of CVS in advance of the version >available on Cygwin mirrors, you may not get much help here. I suggest you >download the source for the Cygwin CVS >(release/cvs/cvs-1.11.0-1-src.tar.gz) and see what is done in the >corresponding places there. If that version has the same problems, I'm >sure the Cygwin maintainer would appreciate a patch. > > > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/