X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_00,FAKE_REPLY_C,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: From: "Lists" To: Subject: Re: Possible Bug or limitation in Cygwin 1.7 and Rsync and file number limit Date: Wed, 1 Jul 2009 13:35:30 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-TRC-MailScanner-Information: Please contact the ISP for more information X-TRC-MailScanner-ID: n61IS1Xt023250 X-TRC-MailScanner: Found to be clean X-TRC-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=2.012, required 5.75, FAKE_REPLY_C 2.01) X-TRC-MailScanner-SpamScore: xx X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 >> On Jul 1 07:36, Lists wrote: >>>> I tried it 6 times in a row, every time erasing the destination files. >>>> Works fine for me. >>>> >>>> >>>> Corinna >>>> >>> Perhaps you have hit upon the problem. I am just downloading and >>> running >>> setup-1.7.exe and it definetly has this problem. I tried to download >>> and >> >> Setup-1.7.exe can't have this problem. What you mean is the Cygwin DLL. >> >>> build it from CVS as you did but I have never done that before and for >>> some reason it isn't working. I'm not even sure if I am downloading >>> code >> >> What are you trying to download and build from CVS? Setup or Cygwin? >> >>> for v1.5 or v1.7 but when I follow the instructions under the FAX, it >> >> No idea what you mean. When you use Setup-1.7 you'll download the 1.7 >> packages. When you download CVS HEAD, you'll download the 1.7 sources. >> >>> won't build. So when will the latest changes be incorporated in the >>> version downloaded in the setup-1.7.exe because it defintely has this >>> problem. I have no doubt about it. >> >> That's fine, but unless I can reproduce it, I can't fix it. You could >> try to debug it yourself. There's GDB, strace, and sources for >> everything. >> >>> problem. I have no doubt about it. Or, is there somewhere else I can >>> find a pre-built version of the latest CVS cygwin1.dll? >> >> http://cygwin.com/snapshots/ >> >> >> Corinna >> > In your earlier reply, you said that you used the latest cygwin from CVS > and that is not what I am using. I am using the cygwin that installs > after running setup-1.7.exe on the web site. I don't know if they are the > same. I do know that the one I am using has this problem as I have > reproduced it far too many times. > > By the way, when I try to build it from CVS, I get the following: > > cc1: /oss/src/newlib/libc/argz/dummy.c: No such file or directory > cc1: /oss/src/newlib/libc/argz/dummy.c: No such file or directory > cc1: /oss/src/newlib/libc/argz/dummy.c: No such file or directory > cc1: /oss/src/newlib/libc/argz/dummy.c: No such file or directory > cc1: /oss/src/newlib/libc/argz/dummy.c: No such file or directory > cc1: /oss/src/newlib/libc/argz/dummy.c: No such file or directory > make[5]: *** [lib_a-dummy.o] Error 1 > make[5]: Leaving directory `/oss/build/i686-pc-cygwin/newlib/libc/argz' > make[4]: *** [all-recursive] Error 1 > make[4]: Leaving directory `/oss/build/i686-pc-cygwin/newlib/libc' > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory `/oss/build/i686-pc-cygwin/newlib' > make[2]: *** [all] Error 2 > make[2]: Leaving directory `/oss/build/i686-pc-cygwin/newlib' > make[1]: *** [all-target-newlib] Error 2 > make[1]: Leaving directory `/oss/build' > make: *** [all] Error 2 > > - Kyle I just discovered some additional information that may help get to the bottom of this. Not sure what made me think of this, but I decided to try an older version of rsync. If I run rsync 3.0.4-1 or 3.0.5-1, I experience the problem. However, when I run 2.6.9-2, the only other version of rsync I can find built specifically for cygwin 1.7, the problem goes away and all works fine? By the way Corinna, in case I didn't say it before, thank you very much for trying to help out and for the time you spend on this project! - Kyle -- 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