Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 14 Aug 2002 10:16:08 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: BUG: fork problems with libxml2 Message-ID: <20020814141608.GD27499@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20020814122645.8526.qmail@web13706.mail.yahoo.com> <17107620139.20020814161126@familiehaase.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17107620139.20020814161126@familiehaase.de> User-Agent: Mutt/1.3.23.1i On Wed, Aug 14, 2002 at 04:11:26PM +0200, Gerrit P. Haase wrote: >This is a problem with Cygwin fork(). You need to rebase the DLL's and >all should work well then. This needs Cygwin core development and >meanwhile one needs to rebase the DLL's if there are problems with fork(). >Hint to the home of Cygwin-rebase: >http://www.tishler.net/jason/software/rebase/ This is not a "cygwin problem" it is a "windows problem". Actually, it isn't even a "windows problem", since cygwin is trying to do something that windows doesn't guarantee can be done. It isn't clear to me that there actually is a solution for cygwin. However, if one was looking for an actual problem then people repeatedly reporting the same "bug" would be a pretty obvious sociological problem. cgf -- 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/