X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.3 required=5.0 tests=AWL,BAYES_20,RCVD_IN_DNSWL_NONE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: From: "Sisyphus" To: References: <468C8EDAC5AC4C82ABF574C6245B394A AT dumbopc> <20120314185022 DOT GB17575 AT ednor DOT casa DOT cgf DOT cx> In-Reply-To: <20120314185022.GB17575@ednor.casa.cgf.cx> Subject: Re: Fw: Cygwin updates cause rebaseall errors Date: Thu, 15 Mar 2012 20:49:02 +1100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit 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 ----- Original Message ----- From: "Christopher Faylor" < > I'd highly suggest not including pointers to random web sites > as a method to fix this issue but, instead, point to the Cygwin FAQ and > the Cygwin mailing list. Seems a sane suggestion to me. I'm a bit dubious about providing a hard link to http://cygwin.com/faq/faq-nochunks.html#faq.using.fixing-fork-failures as it seems like the sort of link that might change. Would "Go to http://cygwin.com/faq/ and see the section 'How do I fix fork() failures?'" be a better option ? But then .... I'm not so sure about the advice offered in that FAQ entry. It says "Read the 'rebase' package README in /usr/share/doc/rebase/, and follow the instructions there to run 'rebaseall'". But, although I have a /usr/share/doc folder, I don't have a /usr/share/doc/rebase/ folder. I can see /usr/bin/rebase.exe and /usr/bin/rebaseall, and I can reproduce the problem that Chloe reported with Inline::C and Cygwin. But I haven't yet fixed it, as I've been unable to work out how to successfully run 'rebaseall'. I'll check this out properly when I get a chance. In the meantime, the question about the "best way" to refer to the relevant Cygwin FAQ entry still stands. Cheers, Rob -- 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