This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: problem with cvs binary?
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 16 Jul 2013 15:10:44 +0200
- Subject: Re: problem with cvs binary?
- References: <ks2e8i$idp$1 at ger dot gmane dot org> <51E54596 dot 5040400 at cwilson dot fastmail dot fm>
- Reply-to: cygwin at cygwin dot com
On Jul 16 09:07, Charles Wilson wrote:
> On 7/15/2013 11:21 PM, Mark Levedahl wrote:
> >The currently provided cvs executable does not work correctly, simple
> >test case is:
> >
> >~>export CVSROOT=/tmp/cvsroot
> >~>cvs init
> >~>cvs co -d /tmp/workdir .
> >cvs [checkout aborted]: cannot make directory : No such file or directory
> >
> >~>cygcheck -c cvs
> >Cygwin Package Information
> >Package Version Status
> >cvs 1.12.13-10 OK
> >
> >~>uname -a
> >CYGWIN_NT-5.1 virt-winxp 1.7.20(0.266/5/3) 2013-06-07 11:11 i686 Cygwin
> >
> >The above should checkout the empty project to /tmp/workdir, but does
> >not work with the binary provided via setup.exe. This does work
> >correctly with a) cvs-1.12.13 rebuilt from sources, and b) with cvs v
> >1.11.22-1 downloaded from setup.exe. The expected result:
>
> Thanks for the report. Rebuilding cvs against current 32bit
> w32api/cygwin is on my list, as well updating the 64bit package.
> However, it comes after (a) mingw-gcc cross compiler & friends, (b)
> automake-X.Y, and (c) libtool. :-(
Are the mingw cross compilers still necessary, now that we have
modern mingw-w64 toolchains? On Fedora they aren't shipped since
F17, which already came with mingw-w64 toolchains either.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple