public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: cygwin@cygwin.com
Subject: Re: problem with cvs binary?
Date: Tue, 16 Jul 2013 13:30:00 -0000	[thread overview]
Message-ID: <51E54596.5040400@cwilson.fastmail.fm> (raw)
In-Reply-To: <ks2e8i$idp$1@ger.gmane.org>

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. :-(

--
Chuck




--
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

  reply	other threads:[~2013-07-16 13:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-16  6:03 Mark Levedahl
2013-07-16 13:30 ` Charles Wilson [this message]
2013-07-16 15:01   ` Corinna Vinschen
2013-07-16 15:52     ` mingw.org cross compiler [Was: problem with cvs binary?] Charles Wilson
2013-07-16 17:05       ` Earnie Boyd
2013-07-17  1:39         ` Charles Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51E54596.5040400@cwilson.fastmail.fm \
    --to=cygwin@cwilson.fastmail.fm \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).